Connect invoice and document data to your accounting software
An accounting integration passes agreed invoice or document information between accounting software and other business tools. What can be shared and how it is processed depends on the software and your accountant's requirements. We first establish which fields and checks are needed.
What information does your accounting software need?
Start with the document or financial detail and the tool where it originates. Your accountant confirms which fields and checks are appropriate for your records. We then review what the software makes available and whether a relevant status can be returned to another tool.
Possible flows include sales invoices sent to accounting software, purchase documents for review, agreed invoice or payment statuses shared with a CRM or ERP, and customer or supplier details. These are questions to discuss, not a promise that a particular combination or accounting treatment is available.
What does your accountant need to confirm?
Your accountant determines which documents, ledger accounts, VAT treatment and checks are appropriate for your situation. BOUT LAST WEEK does not provide accounting or tax advice through this service. We align the technical data flow with the requirements agreed with your accountant and decide which cases need a person to review them.
What happens when information is incomplete or rejected?
A document with missing details or an error should not be treated as processed without confirmation. We agree who receives the information, how the cause is checked and how a corrected document can be submitted again. The error details and statuses available depend on the software.
How do we assess an accounting integration?
We first confirm the required documents, fields and checks with your accountant. Then we review the source software, available fields, account access and existing connections. We agree who checks incomplete or rejected documents and how corrections are handled. The proposal sets out the feasible data flow, deliverables, responsibilities, price and schedule.
Start with your accountant
Your accountant confirms the information and checks the accounting software needs.
Check the source and software
We review the source, available fields, software features and access rights.
Agree on corrections
We agree who checks incomplete documents and handles corrections.
Set the scope
The proposal defines the data flow, deliverables, responsibilities, price and schedule.
What affects the cost of an accounting integration?
The scope depends on document types, sources, fields, checks and any status updates. Your accountant's involvement, existing features and correction steps also matter. The proposal sets out deliverables, assumptions, exclusions, responsibilities, access, price and schedule, along with relevant recurring costs and who manages and pays for each account.
Looking for a particular tool?
Common questions
Yes, when you are deciding which documents, fields and checks are needed. Your accountant confirms the accounting requirements; we can then assess the technical options.
That depends on your accountant's requirements and the software you use. We first agree which documents and checks are needed, then assess which data flow is available.
The available error details and next steps vary by software. We agree who receives the notice and how a corrected document can be submitted again, where the software allows it.
Not necessarily. Sending documents and processing bank transactions may require different features, access rights and agreements. We scope the required step separately.
Which documents need to reach your accounting software?
Tell us where the documents are created, which accounting software you use and what your accountant needs to check. We can then discuss the right next step.