Work snippet
Recurring maintenance contract billing from Airtable into Xero
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
A few hundred service contracts, some billed monthly, some quarterly, some once a year in advance. Contract terms live in an Airtable register; on the 25th Make drafts the following month’s Xero invoices, and anything out of the ordinary, such as a price review, a pause or an end date, is held for review first.
The problemXero repeating invoices drift as contracts change: missed price reviews, ended contracts still billing.
What changesOne contract register drafts every invoice due, and anything unusual waits for a person.
- Area
- Recurring billing
- Tools
- Airtable · Xero · Make · Slack
- Typical scope
- US$350-800
- Timeline
- About 5 weeks · fixed milestones
The situation and what was breaking
Xero’s repeating invoices coped until contracts started changing mid-term: price rises, paused sites and extra visits all needed hand edits that were easy to miss.
Each contract had been set up as a Xero repeating invoice. Price reviews were applied by hand, sometimes late, pauses were done by deleting the template, and contracts that ended kept billing until a customer called. Nobody could produce a list of active contracts and what they should bill next month.
The owner wanted the terms in one place and the invoices drafted from it, with a person approving anything that changed.
- Price reviews applied months late
- Ended contracts still billing
- Paused contracts deleted and lost
- No list of what should bill next month
- Annual contracts missed when the template was edited
What good looks likeOne register of contracts, and next month's invoices drafted from it for me to approve.
Discovery findings
What a read-only review checks first: an export of the Xero repeating invoice templates, the contract PDFs on file, and 12 months of recurring invoices issued.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Templates with no matching contract | 27 templates | Billing with no agreement on file |
| F2 | Price reviews overdue | 41 contracts past their review date | Revenue left behind |
| F3 | Ended contracts still billing | 6 in 12 months, $8,920 credited | Credits and complaints |
| F4 | Paused by deleting the template | 11 contracts | History and terms lost |
| F5 | Annual contracts billed on the wrong month | 4 cases | Cash timing and disputes |
| F6 | No owner for the monthly run | Run by whoever noticed | Missed months |
Architecture: Xero recurring invoices
Terms live in Airtable. On the 25th, Make reads every contract due next month, drafts invoices in Xero, and holds the ones that need a person. Nothing is approved or sent automatically.
Scroll sideways to see the full drawing
The screens your team will use
The office maintains contracts in Airtable and approves drafts in Xero. The run summary arrives in Slack on the 25th.
Contract register
| Contract | Cycle | Price | Next bill | Review | Status |
|---|---|---|---|---|---|
| MC-0412 | Monthly | 420.00 | 1 Nov | Mar | Active |
| MC-0418 | Quarterly | 1,260.00 | 1 Nov | Jan | Active |
| MC-0433 | Annual | 5,880.00 | 1 Nov | Due now | Review |
| MC-0447 | Monthly | 310.00 | 1 Nov | Jun | Paused |
| MC-0452 | Monthly | 890.00 | 1 Nov | Feb | Ends 30 Nov |
Price, cycle, next bill date and review date are the only fields the run reads.
November drafts are ready in Xero.
The run posts once. Held contracts have no draft until the office resolves them.
The next bill date only moves forward after the Xero draft exists, so a failed run can be rerun safely.
How it is built
Register first, then migrate from the templates, then run in parallel for one month before the templates are switched off.
- Module ARegister design
Contract, customer, cycle, price, start, end, review date, pause, Xero contact and item.
- Module BMigration
412 templates matched to contract PDFs; 27 with no contract listed for a decision.
- Module CRun rules
Standard, review due, paused, ending, new, and annual in the wrong month each get a rule.
- Module DDraft creation
One draft per contract per period, with the contract id in Reference.
- Module EIdempotent rerun
The next bill date moves only after the draft exists, so reruns cannot double-bill.
- Module FParallel month
Drafts compared to the old templates for one month, then templates switched off.
Field mapping and rules
The register is small on purpose. Every field it has is used by a rule.
| Airtable | Xero | Rule |
|---|---|---|
| Contract id | Reference | Required, used for reruns |
| Customer | Contact | Linked by Xero contact id |
| Price | Line amount | Reviewed price once approved |
| Cycle | Period on line description | Monthly, quarterly, annual |
| Next bill date | Invoice date | Moves forward after draft |
| Item code | Item | Fixed list of service items |
| Case | Result |
|---|---|
| Standard | Draft created |
| Review date passed | Held until the new price is approved |
| Paused | No draft; pause end date checked |
| End date in the period | Final draft prorated, then contract closed |
| New, no start date | Held |
| Annual, month differs from start | Held |
Worked figures
Walkthrough arithmetic: the first run from the register, for one month.
November drafts by cycle
QA and testing checklist
Every check runs in a copy or on test records first, and each one is ticked with evidence before go-live.
- T1StandardA monthly contract creates one draft at the register price.
- T2ReviewA passed review date holds the contract.
- T3PauseA paused contract creates no draft.
- T4EndAn ending contract bills prorated, then closes.
- T5Annual monthAn annual contract drafts only in its start month.
- T6RerunRunning twice in a month creates no second draft.
- T7ParallelNovember drafts equal the old templates, apart from listed changes.
- T8Nothing sentNo draft is approved or emailed by the run.
Scope
| Area | Included |
|---|---|
| Review | Templates, contract PDFs and 12 months of recurring invoices, with findings |
| Register | Airtable base with views for due, held and reviews |
| Migration | Templates matched to contracts, gaps listed |
| Run | Make scenario on the 25th, drafts only, rules and holds |
| Parallel month | Compared with templates, then templates off |
| Not included | Contract wording, pricing decisions, or Airtable plan costs |
Milestones, week by week
- Week 1
Review and design
- Template export
- Register design signed
- Week 2
Migration
- 380 contracts in Airtable
- Gaps listed
- Week 3
Run built
- Rules and holds on a copy
- Rerun tested
- Week 4
Parallel month
- Drafts against templates
- Differences explained
- Week 5
Handover
- Templates off
- SOP
- 14 days of fixes
Handover and keeping it running
Handover pack
- Billing SOP the 25th to the 1st, step by step
- Register guide adding, pausing, ending and reviewing a contract
- Run rules what holds a contract and why
- Recorded walkthrough register, scenario and Xero drafts
- Ownership list Airtable, Make and Xero in the business's name
- 14 days of fixes for defects in the agreed scope
Keep it running
The run is only as good as the register. A monthly review view lists contracts with a review date in the next 60 days, so price rises are decided before the run, not after.
- 25th: run summary checked, held list cleared by the 28th
- Monthly: review view for the next 60 days
- Quarterly: contracts with no review date listed
- Optional support hours at US$35 per hour, agreed in writing
Typical scope for this kind of project: US$350-800
About 5 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.