Build a MYOB receivables and payables chase list

This job is about collection and payment timing, not overall performance. It answers: who must we chase, who must we pay, and in what order. Do not turn it into a profit review; if the user wants the whole-business picture, that is a different job.

1. Confirm the business file and the as-at point

Call myob_get_business_info first. Confirm the file name with the user before going further, since a chase list for the wrong business is worse than no list. Then call myob_get_financial_year_dates to fix the period. Outstanding balances are a point-in-time view, so state the as-at date you are working from. If the user says "overdue", check the date against the payment terms in step 3 rather than assuming today's date.

2. Pull the outstanding balances on both sides

Call myob_get_outstanding_customer_balances for money owed to the business and myob_get_outstanding_payables for money the business owes. Work out each side separately. Do not net them off in the same list: a customer who owes you and a supplier you owe are different follow-ups, even if they are the same name.

Read each balance by amount and by age. Age buckets are the working unit of collections (current, 1–30, 31–60, 61–90, over 90 days past due). If the tool does not return age directly, say so and rank by amount only, labelled as such.

3. Apply the standard payment terms

Call myob_get_standard_payment_terms and use it to decide what counts as overdue. A balance 10 days past due on 30-day terms is not the same as on 7-day terms. Where a customer's terms differ from the standard you have been given, flag it rather than guessing. Never invent a term that the tool did not return.

4. Rank the receivables

Rank by overdue amount first, age second. A large amount 90 days old outranks a larger amount 5 days late, because the older debt is the one at risk. Put the top five on the chase list and group the rest.

Watch for these before chasing:

• a balance that is only slightly overdue on large terms, which is a reminder, not a call
• a customer with several overdue lines, which is one conversation, not several

5. Rank the payables by due date, not by size

For bills, the question is what must be paid to avoid penalties or supply disruption, and what can wait. Order by due date, then amount. Flag any bill already overdue. Do not recommend withholding payment to a supplier to protect cash without the user deciding that.

Common patterns and traps

• One customer, many invoices. Summing the lines gives the true exposure; chasing each invoice separately annoys the customer. Present one row per customer.
• Old debt that is probably uncollectable. A balance over 90 days with no recent payment is a write-off candidate. Say so and recommend the user review it; do not decide it.
• Terms mismatch. The standard terms are not every customer's terms. Flag rather than assume.
• Timing masquerading as risk. A bill due tomorrow is not an emergency. Keep "due soon" separate from "overdue".
• Confusing receivables with revenue. Money owed to you is not income you have earned in cash. Keep the wording clear.
• Missing tool results. If a call returns nothing or fails, say the list is incomplete. Do not present a partial list as complete.
• Scope creep into tax or payroll. Overdue tax or payroll liabilities are outside this connector. Say so and stop there.

Output

As at: <date>   Business: <file name>   Terms basis: <standard terms used>

Chase now (customers, ranked by overdue amount, then age)
1. <customer> — <overdue amount> overdue, oldest <n> days, <number of lines> lines
2. ...

Monitor (current or <30 days overdue)
- <customer> — <amount>

Pay soon (suppliers, ordered by due date)
1. <supplier> — <amount> due <date>, overdue: <yes/no>
2. ...

Not established: <missing age data, terms mismatches, failed calls>

Rules

• Read-only. Do not write, change or send anything from this connector.
• Do not send reminders, emails or payments. Drafting a reminder message is fine; sending it needs the user's explicit yes.
• Do not recommend withholding supplier payments or writing off debt; present the options and wait for the user's decision.
• Never present a figure you did not get from a tool result as if it came from MYOB.
• Never treat a standard term as a specific customer's term without checking it.

Done when

• The business file and as-at date are confirmed and stated.
• Receivables and payables are ranked separately, each by the stated rule.
• Overdue status is judged against the payment terms the tool returned.
• The "Not established" line is honest about missing ages, mismatched terms or failed calls.