Send your invoices to your accounts
Push the month's documents into your accounting system, and deal with anything that bounces.
The sync usually runs by itself overnight. You come to this screen to check it worked, to push something immediately, or to deal with a failure.
1. Preview what will go
Payments → Accounting Sync, then Refresh preview. It shows the documents waiting to be sent.
The preview is built by exactly the same process as the real run, so it is not an approximation — what you see is what will be posted.
2. Run it
Choose the sync button for your accounting system. Documents go in a fixed order — customers first, then invoices, then credit notes, then payments, then the settlements between them.
That order is a requirement, not a preference: an invoice cannot be posted before the customer it belongs to exists.
3. Read the result
Each batch reports Synced, Failed and Skipped, with a row per document showing Type, Reference, Status, Tries and Why it failed.
- Failed — your accounting system rejected it. The reason is shown verbatim.
- Skipped — it depends on something that failed. Fix the cause and the
dependent goes on the next run.
4. Fix and retry
Most failures are one of two things:
- An unmapped package type — map it, then Retry. See
Map your packages to your accounts.
- Something your accounting system objects to — a missing customer field, a
closed period. Fix it there, then retry the document.
Retry re-sends a single document rather than the whole batch.
What is never sent
- Anything dated before your cutover date.
- Draft or voided invoices.
- Payments that have not succeeded.
- Anything imported as pre-migration history.
E-invoices
Submitting e-invoices to the tax authority is your accounting system's job, not Hull's. Hull records which invoices a buyer asked to receive individually and which are rolled into the consolidated submission, and passes that along.
Related: Connect your accounting system · Close the month · Invoices, payments and credit notes.