Loaditude and Xero
Invoice the work you actually did, and have it land in Xero correctly the first time
Most accounting integrations do not know what a job is
They can post a total. They cannot tell your customer which delivery it was for, what their purchase order was, or what the installation cost separately from the transport. So the invoice gets queried, and somebody spends a morning proving what was already recorded. Loaditude invoices from the jobs themselves, which is why the detail survives the journey into Xero.
Invoices, one or a hundred
Raise an invoice from the jobs you delivered and send it to Xero as a draft, on its own or as a batch. Nothing is issued to a customer automatically, so a mistake is always recoverable.
- Push a single invoice, or a whole selection at once
- Every invoice reported back by number, not as a count
- An invoice already in Xero is recognised, never duplicated
- Created as a draft for you to review and approve
The detail their accounts team needs
The customer's purchase order goes in the Reference field, which is what accounts payable match on, and every line names the job it came from.
- Purchase order and customer reference on the invoice and each line
- Transport, and extras such as checks or installation, as separate lines
- The job number, route and date of the work on every line
- Several jobs with different purchase orders on one invoice
Your chart of accounts, not ours
Choose the account code invoices post to, with warehousing able to post separately from transport. Left unset it uses Xero's default sales account.
- Account code set once, per company
- Separate code for warehousing where the books separate it
- Owner and administrator only
- Applies to invoices sent from then on
Two systems that agree
Xero's own invoice number and status are shown against the invoice here, and payment status comes back automatically when an invoice is settled.
- Xero's invoice number and status, in plain words
- Marked paid here when it is paid there
- Correct an invoice and send it to Xero again
- Told plainly when Xero will not accept a change
Stop re-keying your own invoices
See how a job becomes an invoice, and an invoice becomes a line in your ledger
Frequently asked questions
Does Loaditude integrate with Xero?
Yes. Connect your Xero organisation once from Settings, and transport and warehousing invoices raised in Loaditude can be pushed to Xero as draft invoices. Loaditude records which Xero invoice each one became, so it is never sent twice.
Can I send several invoices to Xero at once?
Yes. Select the invoices and push them in one action. Each is reported back individually by invoice number, so if Xero refuses one you are told which and why, rather than seeing a count of failures.
Does the customer's purchase order reach Xero?
Yes. Xero has no separate purchase-order field, so Loaditude puts the customer's PO in the invoice Reference, which is what most accounts payable teams match against, followed by your own invoice number so it can still be traced back. Where one invoice covers several jobs with different purchase orders, all of them appear and each line names its own.
Which account do invoices post to in Xero?
You choose the account code from your own chart of accounts, and warehousing can post to a different account from transport. If you do not set one, Loaditude uses Xero's default sales account, 200.
What happens if I correct an invoice after sending it to Xero?
You can send it again and Xero is updated with the corrected version. Xero will not allow an invoice that has been paid, voided or deleted to be changed, and in that case Loaditude tells you which it is and what to do instead, such as raising a credit note.
Does Loaditude know when an invoice has been paid in Xero?
Yes. With webhooks configured, Xero notifies Loaditude when an invoice is settled and it is marked paid here with the payment date, so you are not reconciling two systems by hand. You can also ask Xero for an invoice's current status at any time.
Are my Xero credentials safe?
Access and refresh tokens are encrypted at rest, the connection is scoped to your own company, and only an owner or administrator can connect, disconnect, or change which accounts invoices post to.