Your next finance tool
could be a prompt.

“Using my Xero data through xpnAi, build a weekly cash forecast for the next 13 weeks in AUD. Start with the latest available cash balance and state its date. Use outstanding invoices and bills for expected receipts and payments. Ask me for payroll, tax, recurring costs and any other missing cash movements before finishing. Show opening cash, receipts, payments and closing cash each week. Flag any week below $50,000. List timing assumptions, distinguish estimates from actuals and link to the source records.”

“Using xpnAi, prepare a management report for last month. Include a profit and loss, balance sheet and a summary of aged receivables and payables. Compare the P&L with the previous month and the same month last year. Explain the five largest account movements, drill into the source transactions and link to supporting records. Finish with a concise executive summary and three questions for the management team. Separate evidence from possible explanations and ask me about anything the ledger cannot explain.”

“Using xpnAi, consolidate my connected Australian, UK and US Xero organisations in AUD for last month. Show the group profit and loss and balance sheet, with a column for each entity. Explain the exchange rates and account mappings used. Identify potential intercompany balances and mapping differences that need review, and state how eliminations are treated. Link material movements to source transactions. Ask me to confirm the entity scope and consolidation assumptions before finalising.”

“Using xpnAi, find outstanding Xero invoices at least 7 days overdue. Group them into 7–13, 14–29 and 30+ day bands. Check remaining balances, credit notes and part payments. Group the invoices by customer. Ask me for known disputes and promises to pay, and exclude those from routine reminders. Draft one email per customer, using the oldest eligible invoice to set the tone: friendly at 7–13 days, direct at 14–29 and firm but courteous at 30+. Include invoice references, remaining amounts and due dates. Show the drafts and source invoices for my review. Do not send anything or change any records.”

“Using my Xero data through xpnAi and payouts and balance transactions from the connected Stripe MCP server, reconcile last month’s automatic Stripe payouts to the receipts recorded in Xero. Confirm the Stripe account, Xero organisation, date range, timezone and settlement currencies first. Retrieve all relevant pages of records. For each payout, bridge gross payments, refunds, fees, disputes and other adjustments to the net amount, then match it to the Xero receipt using payout references, amount, currency and timing. Keep currencies separate and distinguish timing differences from missing or duplicate entries. Do not assume manual payouts have transaction-level allocation. Show matched payouts, unexplained differences and source record references. Identify any missing data or MCP permissions before concluding. Do not change records.”

“Using xpnAi and my Employment Hero Payroll data through a connected third-party MCP provider such as SyncHub, reconcile last month’s finalised payroll to Xero. Confirm that the connection exposes the required pay runs, payslip totals and journal account mappings, and state its latest sync time. Confirm the employing entity, pay run IDs, pay dates, earning periods and currency. Compare gross wages, employer contributions, employee deductions, tax withholdings and net pay with the corresponding Xero expense and liability entries. Match by pay run reference and account, identify missing or duplicate journals and separate timing differences from mapping errors. Show expected amounts, ledger amounts and differences, with source record references and Xero links. Ask for the mapping of any unfamiliar payroll code. Identify unavailable data or permissions before drawing conclusions. Prepare an exception list for review and do not change payroll or accounting records.”

“Using xpnAi and invoice details, fee invoices, payment receipts and payment breakdowns available through the connected Deel MCP server, reconcile last month’s contractor costs to Xero. Confirm the contracting entity, period, currencies and account mappings. Check the invoice statuses and dates covered by the available tools, and identify any gaps in unpaid invoices or funding history. Match invoice references, contractor costs, reimbursements and platform fees to Xero bills and ledger entries. Reconcile available funding and settlements separately so a wallet top-up or funding transfer is not counted again as an expense. Keep original-currency amounts separate from reporting-currency amounts and use the exchange rates and policies I provide. Identify missing or duplicate bills, fees, credit notes, unsettled balances and FX differences. Show source record references and an exception list. Identify unavailable data or MCP permissions and do not create bills, journals or payments.”

“Using employee and people data available through the connected HiBob MCP server, finalised payroll data from my connected payroll provider, and Xero data through xpnAi, reconcile last month’s people records to payroll. Confirm the employing entities, pay periods, payroll cut-off and employee ID mapping. Check the connected tools and permissions for effective-dated starters, leavers, salary changes, FTE and leave-related changes; do not infer historical changes from a current employee snapshot. Compare available records with payroll, taking effective dates and approved exceptions into account. Flag missing, duplicate and unexpected paid employees, but ask me to explain exceptions before treating them as errors. Bridge payroll totals to the Xero payroll journal; do not assume the ledger contains employee-level detail or that HiBob provides the payroll register. Use employee IDs and source record references in the review list. Identify unavailable data or permissions and do not change HR, payroll or accounting records.”

“Using my connected Xero data through xpnAi, review last month’s supplier bills for missing supporting attachments. Confirm the organisations, period and statuses to include, and retrieve all relevant records. Distinguish bills confirmed to have no attachments from bills whose attachment status is unknown or unavailable. Show supplier, bill number, date, amount, currency, status, account coding and a source link. Rank missing-evidence items by value, flag duplicates and ask about approved exceptions or evidence held elsewhere. If the connection cannot inspect attachment metadata, state that limitation rather than marking a bill as missing evidence. Give me a follow-up list for review. Do not change bills or send messages.”

“Using xpnAi, reconcile intercompany loan balances between my connected Xero organisations at last month-end. Confirm the lender, borrower, loan currency, period and counterpart loan-account mappings. Use confirmed account roles where available rather than guessing from account names. Roll forward each side from opening balance through advances, repayments, agreed interest, adjustments and FX revaluation to closing balance. Compare principal and interest separately in the loan currency, then explain differences in each entity’s functional currency and the group reporting currency using the approved FX policy. Ask me for agreed interest terms rather than assuming rates. Identify one-sided entries, timing differences, unmatched transactions and mapping errors with source links. Show proposed corrections for review only; do not post journals, change loan terms or move money.”

“Using xpnAi, identify my largest outstanding customer invoice. Build a base 13-week cash forecast from open invoices, bills and the cash assumptions I provide. Then move that invoice receipt two weeks later. Compare weekly closing cash in both scenarios, show the lowest cash point and identify any week below my $50,000 buffer. State the starting cash date and every assumption. Ask me for missing inputs rather than inventing them. Do not change any Xero records.”

“Using my Xero data through xpnAi, compare revenue, cost of sales and gross margin for the last three completed months. Show the account-level changes and investigate the largest source transactions behind the movement. Break the analysis down by tracking category where available. Flag unusual or one-off costs and link to the source records. Distinguish what the data proves from questions I need to investigate.”

“Using xpnAi, prepare an aged receivables report as of today across my connected Xero organisations. Separate current, 1–30, 31–60, 61–90 and 90+ days overdue. Show the ten largest overdue customer balances, the invoices behind each balance and source links. Keep currencies separate unless you can state the conversion method. Flag credit notes, part payments and concentrations that affect the totals. Finish with a concise collection-priority summary.”

“Using xpnAi, create a prioritised collection list from overdue Xero invoices. Rank customers by overdue balance and days overdue, showing payment history where available. Explain the ranking and include invoice references, remaining balances and source links. Ask me for disputes, promised payment dates and important relationship context. Suggest the next action for each customer, with a draft call note or email. Do not infer creditworthiness, send messages or change records.”

“Using xpnAi and balance transactions from the connected Stripe MCP server, reconcile my Stripe clearing account in Xero at last month-end. Confirm the accounting policy, mapped accounts, timezone, each settlement currency and a verified opening Stripe balance. Retrieve all relevant pages and build an opening-to-closing balance bridge for payments, refunds, fees, disputes, payouts and other adjustments, using the source transaction signs and classifications. Compare that balance with the Xero general ledger and identify unsettled payouts, cut-off differences, missing fees and duplicate postings. Do not treat today’s Stripe balance as a historical month-end balance. Keep available, pending and reserved balances distinct where the connected tools provide them. Show supporting source references, unresolved differences and proposed correcting entries for review only. Identify missing data or MCP permissions and do not post anything.”

“Using xpnAi and my Employment Hero Payroll data through a connected third-party MCP provider such as SyncHub, reconcile month-end payroll liability accounts in Xero. Check the available payroll, contribution and payment records and state the connection’s latest sync time. Confirm the entity, jurisdiction, reporting date, opening balances and relevant accounts. For wages payable, tax withholdings, deductions and employer contributions such as superannuation or pensions where applicable, show opening balance plus payroll amounts less payments and adjustments equals closing balance. Match connected payment records to the relevant payroll period and identify unsettled payments, duplicates and unexplained balances. Keep timing items separate from errors and reference the supporting payroll and Xero records. Identify missing payment evidence, data or permissions rather than assuming a balance has been settled. Ask for policies rather than inferring statutory rules. Do not post journals or initiate payments.”

“Using xpnAi and payslips, invoices and payment records available through the connected Deel MCP server, reconcile last month’s payroll costs to Xero by legal entity, country and currency. Confirm the finalised payroll periods, whether each population is direct payroll or employer-of-record, and the accounting treatment and account mappings I provide. Check which wage, employer-cost, reimbursement and fee fields the available tools expose; identify any missing employer costs or funding records before reporting a complete reconciliation. Compare supported amounts with Xero journals or bills, keeping service fees and funding movements separate. Use approved exchange rates for any reporting-currency comparison and explain FX and cut-off differences. Flag missing, duplicate and misclassified entries with source record references and Xero links. Do not add gross payroll to an invoice if that would count the same cost twice. Ask for missing policies, identify unavailable data or permissions, and do not change records.”

“Using department and employee data available through the connected HiBob MCP server, finalised cost allocations from my connected payroll provider, and Xero data through xpnAi, reconcile last month’s people costs by department. Confirm employee IDs, employing entities, payroll periods and the mapping from departments to Xero tracking categories. Check whether effective-dated department assignments and allocation percentages are available to this connection before comparing them with payroll costing, then reconcile supported totals to Xero. Treat mid-period transfers and shared roles using the allocation policy I provide; do not assume current departments reflect historic assignments, everyone is allocated entirely to one department, or annual salary equals monthly expense. Flag missing tracking, unmapped departments and unexpected differences with source record references. Identify missing data or permissions and suggest reallocations for review only. Do not post changes.”

“Using xpnAi, review last month’s Xero Spend Money bank transactions for missing attachments across my connected organisations. Exclude payments of supplier bills and bank transfers so the same spend is not counted twice. Confirm the period, currencies, statuses and evidence policy. For each transaction confirmed to have no attachments, show date, payee, bank account, reference, amount, currency, expense account, tax code and source link. Keep unavailable attachment metadata separate from confirmed missing receipts. Prioritise higher-value or unusual items and identify approved policy exceptions separately. Prepare a follow-up list without treating a missing receipt as proof of an invalid expense. Do not change transactions or contact anyone.”

“Using my connected Xero data through xpnAi, create an exception report of expenses strictly over $1,000 for last month. Confirm the organisations, reporting currency, tax basis and transaction statuses first; use AUD 1,000 excluding tax per source expense transaction unless I specify otherwise. Sum expense-coded lines within each source document and count the document once. Include supplier bills, Spend Money transactions and expense journals, without duplicating their general ledger entries or counting bill payments and bank transfers as expenses again. Show date, supplier or payee, reference, entity, expense accounts, cost centre where available, expense amount, currency and source link, largest first. Keep credits, refunds and reversals separate. For foreign-currency items, state the approved conversion method before applying the threshold. Show the exception count and total, with missing data or approved policy exceptions identified. Do not change records or send messages.”

“Using xpnAi, create an exception report for last month’s petty cash spending with no cost centre assigned. Ask me to confirm the petty cash accounts, organisations and the Xero tracking category that represents cost centre; do not infer petty cash from a small amount alone. Inspect expense lines on the relevant petty cash transactions and flag each line whose cost-centre option is confirmed blank. Distinguish entirely unassigned transactions from documents where only some lines are missing a cost centre. Exclude float top-ups and bank transfers, and show credits or reversals separately. Show date, payee, reference, entity, petty cash account, expense account, affected line amount, currency, current tracking and a source link. Report the distinct transaction count and total of affected expense lines by currency without double counting. Keep unavailable tracking metadata separate from confirmed missing coding. Propose any likely cost centres for review only, using rules I confirm; do not assign them or change transactions.”

“Using my connected Xero data through xpnAi, create an exception report of possible duplicate supplier bills and sales invoices. Confirm the organisations, review period, document statuses and comparison lookback window. Compare supplier bills with other supplier bills and sales invoices with other sales invoices within the same entity; do not treat an intercompany bill and invoice pair as duplicates. Group candidates using contact, currency, normalised reference, amount, date and line details where available. Separate exact field matches from near matches, explain the matching rules and flag missing fields. Check payments, credit notes, voids and recurring charges so valid repeats and corrections are not automatically treated as errors. Show each candidate group, source links, payment status and the reason for review. Count each group once and distinguish total document value from possible additional duplicate exposure. Ask me to confirm exceptions before any action; do not void documents, issue credits or change records.”

“Using xpnAi, create an exception report of unusual manual journals for last month across my connected Xero organisations. Confirm the materiality threshold, currencies, sensitive accounts and the review rules to apply. Flag journals above the threshold, unexpected account combinations, round-number entries, missing or vague narrations, and late or backdated postings where the available timestamps support that check. Show journal reference, date, entity, status, narration, debit and credit accounts, value, tracking, source link and the specific rule triggered. Include creator, approval and supporting-evidence details only where available, and label unavailable history rather than inferring it. Separate drafts from posted entries and identify linked reversals or recurring journals. Count each journal once, showing total debits and credits separately instead of doubling its value. Rank the review list by materiality and explain every flag without treating it as proof of an error. Do not post, reverse or change journals.”

“Using my Xero data through xpnAi, create an exception report of unresolved transactions sitting in suspense accounts at last month-end. Ask me to confirm the account IDs, organisations, currencies, reporting date and ageing threshold rather than selecting accounts by name alone. Reconcile the opening balance and all movements to the closing balance, including unresolved items originating before the review period. Show source transaction, original date, reference, counterparty where available, debit or credit, remaining amount, age, currency, account and source link. Only treat items as cleared when the linked settlement or reclassification is supported; similar amounts or a zero net balance are not sufficient. Report gross unresolved debits, gross unresolved credits and the net balance separately, and flag old, material or insufficiently documented items. Identify missing opening-item detail and propose investigation or recoding for review only. Do not clear balances, net unrelated items or post changes.”

“Using xpnAi, review general ledger accounts created in the last seven days across my connected Xero organisations. Confirm the timezone and exact date window. Use creation evidence or an approved earlier chart snapshot where available; do not treat a last-updated or first-synced timestamp as proof of creation. Label accounts that are only newly observed separately. Show entity, account code, name, type, tax setting, status, available creation evidence and source references. Flag duplicate purposes, code collisions, unusual account types and differences from the group chart. If creation history or a suitable baseline is unavailable, state what can and cannot be established. Prepare findings and proposed corrections for review only; do not create, archive or change accounts.”

“Using xpnAi, review changes to Xero contact bank account details over the last seven days across my connected organisations. Confirm the timezone, source history or approved comparison baseline, and data freshness. Distinguish verified bank-detail changes from contacts changed for another reason. Show contact, organisation, change time and actor where supported, masked before-and-after details where available, and source references. Highlight affected outstanding bills for review, without treating a change as proof of fraud or a new account as verified. If historical values or the actor are unavailable, label those gaps explicitly rather than inventing them. Prepare an independent-verification checklist for the finance team; do not edit bank details, approve payments or contact suppliers.”

“Using xpnAi, compare the live charts of accounts across my connected Xero organisations against the group reference chart I confirm. Match by accounting purpose, not just identical names or codes. Identify missing accounts, duplicate purposes, code collisions, account-type differences, archived records and local tax settings that need review. Show each entity’s existing record and a proposed mapping or change, preserving destination record IDs. Keep legitimate local differences explicit and do not assume an unmatched account should be archived. Separate changes to Xero accounts from changes to group reporting mappings. Check required permissions and present a concrete entity-by-entity alignment plan for approval. Do not create, update or archive anything until I approve the exact changes.”

“Using xpnAi, compare live tracking categories and options, including archived records, across my connected Xero organisations. Ask me to confirm the group definitions for departments, locations and other dimensions. Identify inconsistent names, missing options, duplicates, archived options and values used for different purposes. Propose explicit entity-specific mappings that preserve existing record IDs and legitimate local distinctions. Check Xero category limits and available chart-management permissions. Distinguish renaming a current option from changing historical transaction coding or group reporting mappings. Show the proposed changes and exceptions for review. Do not create, rename or archive tracking records, or recode transactions, until I approve the exact changes.”

“Using xpnAi, reconcile interentity cash transfers between my connected Xero organisations for last month. Confirm the entity pairs, bank accounts, counterpart due-to and due-from accounts, currencies and acceptable timing window. Match the sending entity’s cash outflow with the receiving entity’s cash inflow using references, dates, original amounts, settlement amounts and currencies. Keep transfers within a single organisation separate from transfers between legal entities. Reconcile the corresponding intercompany balances, identify one-sided or duplicate postings, and show timing, bank-fee and FX differences separately. Do not force a match from similar amounts alone. Distinguish loan funding, repayment, capital contributions and other transfers using the purpose I confirm. Link both entities’ source records and propose any missing balanced accounting entries for review only. Do not initiate transfers or post changes.”