How the integration works
Supplier invoices arrive in your accounts inbox. The integration checks them against your purchasing records. Matching invoices become unapproved draft bills in Xero. Anything that doesn’t match is held for review with a clear explanation.
-
Reads the invoice details and line items from supplier PDFs in your accounts inbox.
-
Checks quantities and prices against your available purchase orders, delivery records and agreed prices.
-
Checks the calculations and VAT against your agreed tolerances, and flags possible duplicates.
What your team receives
- If all checks pass:
- Your team receives an unapproved draft bill in Xero, with the supplier's PDF attached and ready for your team to review.
- If something needs attention:
- The invoice is held for review. Your reviewer sees the reason, such as a price difference, missing record or possible duplicate, and decides whether it needs correcting, should be rejected, or can proceed to Xero as an unapproved draft bill.
Your team approves and pays bills.
When does a custom integration make sense?
Start with an existing tool. If it can handle your invoices, purchasing records and approval process, use it.
If it can't, custom integration starts to make sense.
Get in touch| An existing toolmay be enough if... | Custom integrationmay make sense if... |
|---|---|
| It can read your supplier invoices | Your existing tool can't access your purchasing records |
| It can compare them with your records | Your matching rules are more complicated |
| It clearly flags what needs attention | Your team is still copying data between systems |
Technical Delivery Assessment
Before you commit to a build, the paid assessment examines your invoice workflow, purchasing records and systems, then gives you a written recommendation on what to do next.
€750 + VAT · FIXED FEE
- Five working days after payment and receipt of the agreed invoice samples, purchasing records and system access
- €750 credited toward your pilot within 30 days
- Findings stay yours either way
What you receive
- A map of your current invoice workflow.
- Findings on your data, system access and security requirements.
- Invoice-matching rules and clear responsibilities for handling exceptions.
- A recommendation: build a pilot, use an existing product, or address the problems identified in the assessment first.
- A defined scope and acceptance tests if a pilot is justified.
- A written report and a call to discuss the findings.
The findings remain yours if you decide not to build.
Engagement process
-
Free first conversation
By email or a 20-minute call, whichever suits you. We discuss your workflow and whether an assessment would be useful. No obligation.
-
Technical assessment
I assess your invoice workflow and systems, then we discuss the written findings and my recommendation.
€750 + VAT Credited towards your pilot when booked within 30 days of the written assessment.
-
Implementation, if justified
I build, test and hand over the agreed integration.
€3,950 + VAT Fixed-scope implementation pilot
Three weeks once agreed inputs and access are ready.
Support: available on request after handover, quoted separately. There is no monthly fee from Endpoint 51.
Pilot scope and terms
- Scope
- One Xero organisation, one accounts inbox, one purchasing source and up to five selected suppliers.
- Delivery and warranty
- Exception alerts to a named reviewer, tests, logs, a runbook and a fourteen-day defect warranty against the agreed acceptance cases.
- Payment milestones
- 50% at booking, 40% at the working demonstration and 10% at handover. Book the pilot within 30 days of the written assessment and its €750 fee is deducted from the pilot price, leaving €3,200 + VAT after the assessment payment.
- After handover
- Before implementation, we agree who in your team will operate the integration. It runs in systems you own, and any later support or changes are quoted separately on request.
Work directly with Simon O'Connor.
I'm an Irish software developer and the founder of Endpoint 51. I handle the assessment, implementation and handover, with the scope and acceptance criteria agreed before the build.
Simon O'Connor is the author of Python Developer: From Requests to Production, a practical guide to building and running Python APIs.