New
Webhooks guide and event reference
Every webhook event Dolfin sends is now documented with its full payload under Webhooks in the API reference —bill.pending_review, invoice.paid, match_group.variance and the rest.The new webhooks guide covers the parts a schema can’t: creating a subscription, verifying the Dolfin-Signature HMAC, the retry schedule, de-duplicating on the event id, and testing against a local tunnel. If you’re polling for bill extraction to finish, subscribing to bill.pending_review replaces that loop.Companies
Group several organisations under a company and handle bills at that level. Create a company, list and retrieve them, patch the details, and list its organisations. Organisations are assigned to and removed from a company as needed.A company has its own bill-forwarding address, so a supplier can send an invoice without knowing which entity it belongs to. Upload or forward a bill to the company, then list unassigned bills, read one, and assign it to an organisation — or discard it. A document that couldn’t be read can be retried. Thecompany_bill.awaiting_organisation webhook fires when a bill is waiting to be assigned.Company inboxes carry the same sender controls as organisation inboxes: list, allow, and remove senders, and review forwards that were rejected.Dismiss a false duplicate
When a bill is flagged as a possible duplicate it can’t be approved until someone decides. Confirm it isn’t a duplicate to clear the flag and let the bill continue through review.Organisation-level AR settings
Read and write AR settings per organisation rather than only per client: get and patch payment terms, invoice numbering, reminder offsets, and CC/Reply-To addresses for a single organisation.Updates
Extraction wording in the AP guides
The AP guides now describe reading a bill document as extraction rather than OCR, and use the currentExtracting and ExtractionFailed states. A bill’s extraction confidence is on the confidence field.