Using Xero with septic job management software
The useful accounting connection starts with a clear decision about which system sends the invoice and which records need checking.

The office approves an invoice in Xero, but the job system sends another copy and starts its own reminders. The customer sees two messages for the same visit and rings to ask whether they’re being billed twice.
An accounting connection needs an agreed workflow. Before switching it on, decide which system sends the invoice and how the office will check payments and failures.
Give each system a job
The operations system holds the service visit: property, tank, technician, field records and charges. Xero holds the accounting work your business manages there. Write down where an invoice starts and who issues it to the customer.
Some offices want to check and send every invoice in Xero. Others prefer sending from the job system and syncing the issued records into Xero. Pick the arrangement that fits your accounts process, then test it with actual examples before enabling automatic customer messages.
Tell technicians which payment instructions to give on site. If invoices wait for an accounts review, the field team needs to know that a completed visit won’t always have a final amount ready immediately.
Match customers before invoices
Start with a small group of known customers. Include a company with several properties, an individual and a customer whose billing name differs from their familiar name. Check how the records match.
Shared email addresses deserve attention. A property manager may receive accounts for several owners, and a family might use one email for more than one customer record. Treat ambiguous matches as a task to resolve, rather than a reason to overwrite the record with the closest name.
Keep system and site records separate from accounting contacts. Importing a billing contact doesn’t tell you which treatment plant sits at a property or when its next service is due. The guide to multiple systems at one property explains that structure.
Test the invoice lines
Use a representative completed job. Check the description, quantities, prices and the account and tax mappings agreed with your accounts team. Include a variable pump-out charge or material line if you regularly use them.
Follow the invoice all the way through the intended process. If the office plans to approve drafts in Xero, confirm it arrives as a draft there and that Rangefront hasn’t already emailed the customer. Check the invoice number and the link back to the relevant service job.
A successful connection test only proves the systems can communicate. It doesn’t prove every invoice line is mapped correctly. Missing account codes or other validation errors need a visible queue and someone responsible for fixing them.
Follow a payment both ways
Record a small, controlled payment through the normal business process and check the resulting balance in both systems. Use an invoice created through the integration. An unrelated older invoice in Xero may have no corresponding job-system record.
Repeat the review for the payment methods you use, including a bank transfer recorded by accounts. Watch for a payment entered manually in both places. The office should understand how the integration identifies existing payments before relying on repeated syncs.
Keep a procedure for credit notes and refunds too. A corrected invoice can leave the operational record and accounting record disagreeing if someone adjusts only one side. Test the supported process, and follow any reported exception through to resolution.
Set up Rangefront Waste
Rangefront Waste can import Xero customers, send invoices and sync payments. Its Xero documentation describes matching rules, supported sync directions and failures. Under Payments, the Accounting system sends invoices setting lets the office issue the job invoice into Xero as a draft for review and sending there.
With that setting active, Rangefront suppresses its invoice emails, texts, overdue reminders and statements. Keep checking the connection status: if the connection is paused or removed, the setting stops applying. Add that to the office handover rather than letting it become a surprise when someone changes an integration.
Review the invoice checklist with the person who owns the books. They should be able to identify an unbilled job, a failed sync and a paid invoice without asking the technician to reconstruct the visit.



