MYOB

Use this when the user mentions a financial year, fiscal year, FY, or FYTD. Reports the financial-year calendar: the current financial year plus the two prior years, so you can translate financial-year phrasings into exact dates. Resolve the dates here before calling a tool with dates where the user's request is for a financial period. Dates only; it makes no data request. <do_not_use_for> Answering data questions: after resolving the dates, call the relevant reporting tool (e.g. myob_get_profit_loss). Questions that mention only plain calendar dates. </do_not_use_for> <hints> - Use when the user mentions financial year, fiscal year, FY, FYTD, or a financial quarter/half, e.g. "FY25", "this financial year". - For the CURRENT financial year, use the returned `today` value as the end date, or omit the end date and let the reporting tool default it. Passing current_fy.end for the year in progress is also safe: reporting tools cap any end date after today at today, so a full-FY request for the current year returns year to date. Use current_fy.end as the reference bound for prior-year comparisons, or for a financial year that has already ended. - fy_quarters_start resolves bare quarter phrasing ("Q1", "Q3") to financial-year quarters. A trailing year in "Qn YYYY" (e.g. "Q1 2026") names the financial year by the `label` convention (named by its END year), so quarter 1 of FY2026 begins in the FY2026 start month, not the FY2026 end year's January. - The result is stable within a conversation; call it once and reuse it. - Only the three returned financial years are queryable by the reporting tools; decline requests for earlier years. </hints> <examples> - "When does financial year start?" - "What are the dates for FY25?" - "Show me profit for this financial year" - "Revenue for the current FYTD" </examples> Returns a dict with these fields: today: The server's current date, YYYY-MM-DD. financial_year_end_month: Last month of the FY (1-12; 6 = June). current_fy: {label, start, end} of the current financial year. previous_fy: {label, start, end} of the prior financial year. fy_before_previous: {label, start, end}, the oldest queryable financial year. fy_quarters_start: FY quarter START MONTHS, in FY order (quarter 1 first), beginning with the financial year's start month. note: Statement of the three-year reporting limit.

myob_get_financial_year_dates

Use this when the user asks who owes money or which customers are at risk. Reports current outstanding and overdue customer balances with at-risk customers. Queries the unpaid invoices report as-at today using invoice terms, then categorises each customer by whether they have any balance in aging buckets beyond the current period (Period 2, 3, or 4). Takes no arguments; the business and date are resolved automatically. <do_not_use_for> Standard payment terms (myob_get_standard_payment_terms), invoice-period totals (myob_get_sales_invoice_totals), or historical payment-speed analysis — no tool on this server provides it. </do_not_use_for> <examples> - "Which customers are at risk?" - "Who owes us money?" - "Show me overdue customers" - "Who are the 60+ day debtors?" - "What is our debtor exposure?" </examples> Returns a dict with the following top-level fields: total_customers_with_unpaid (int): Total number of customers that have at least one unpaid invoice. at_risk_count (int): Number of customers whose overdue amount (Period 2 + 3 + 4) is greater than zero. total_outstanding (float): Sum of TotalAmountDue across all customers with unpaid invoices. at_risk_customers (list): Up to 10 customers with overdue amounts, sorted by overdue_amount descending (highest risk first). all_customers (list): Up to 20 customers with unpaid invoices, sorted by overdue_amount descending. Each customer entry in at_risk_customers and all_customers contains: customer (str): Contact name, or the quarantine marker when the complete name fails structural validation. total_outstanding (float | None): Total amount currently owed. overdue_amount (float): Sum of Period 2, 3, and 4 balances; zero means the customer is current (within terms). is_at_risk (bool): True when overdue_amount > 0. aging (dict): Breakdown by aging bucket, keyed by a Platform-controlled, whitespace-trimmed period title (e.g. "Current", "1-30 days", "31-60 days", "61+ days"). Falls back to "Current", "30+ days", "60+ days", "90+ days" when the API omits titles. Optional fields present only when the API supplies a value: avg_days_to_pay (int): Historical average days to pay for this customer (useful for assessing chronic late-payers). customer_terms (str): The payment terms set for this customer (e.g. "30 days"), or the quarantine marker when the complete field fails structural validation. last_payment_date (str): Canonical ISO date or date-time of the most recent payment received from this customer. When no customers have unpaid invoices, returns: at_risk_customers (list): Empty list. total_outstanding (int): 0. message (str): Explanation that no unpaid invoices were found. Per-customer historical payment speed and terms appear here only as the optional fields above, and only for customers with unpaid invoices; this is not a payment-speed analysis tool, and no tool on this server provides one. For the business-default terms use myob_get_standard_payment_terms. Retrieval failures raise a tool error.

myob_get_outstanding_customer_balances

Use this when the user asks how much the business owes suppliers. Reports the total owed, the payables control-account balance, any out-of-balance amount, and the largest supplier balances, as at today or an optional past date (e.g. what was owed at the end of last quarter). This is total amounts outstanding and per-supplier balances, not an aging or overdue breakdown. The business is resolved automatically. <args> as_at_date: Optional snapshot date in YYYY-MM-DD form. Defaults to today when omitted. Must fall within the last 3 financial years and cannot be in the future; out-of-range dates raise a tool error. </args> <do_not_use_for> Profit-and-loss or expense questions — use myob_get_profit_loss for those. This is supplier payables (amounts still owed to suppliers), not an expense report: an amount owed is a liability, not a recognised expense for the period. </do_not_use_for> <examples> - "How much do I owe my suppliers?" - "Show me outstanding bills" - "What is my accounts payable balance?" - "How much did we owe suppliers at the end of last quarter?" - "Give me a payables / creditors overview" </examples> Returns a dict with the following top-level fields: total_outstanding (float): Total amount owed across all suppliers. payables_account_balance (float): The payables control account balance. out_of_balance (float): Difference between the report total and the control account balance; non-zero indicates a reconciliation discrepancy. as_at_date (str): Snapshot date used for the query (YYYY-MM-DD). supplier_count (int): Number of suppliers with a non-zero amount due. suppliers (list): Up to 10 suppliers with the largest absolute amount due, highest first. Each entry contains: name (str): Supplier name, or the quarantine marker when the complete name fails structural validation. amount_due (float): Amount owed to this supplier. A negative value is a credit or overpayment (money the supplier owes the business), not an amount owed. tax_amount (float): GST / tax component of the outstanding amount. When summarising the result, name the single largest payable by supplier and amount. Suppliers are ranked by absolute amount due, so a large credit (negative amount_due) can appear at the top of the list — surface such negatives explicitly as overpayments / credits rather than amounts owed. Retrieval failures raise a tool error.

myob_get_outstanding_payables

Use this when the user asks a profit-and-loss question. Reports the full P&L for a date range (income, expenses, and profit by section, on an accrual or cash basis), and optionally every child account (include_children=true). Only data for the last 3 financial years can be returned. Prior-year comparison fields are always included, computed by the API against the same window one year earlier; report them as returned. Since to_date defaults to today, that means year to date against the same period last year, not a full prior year. <do_not_use_for> Bank cash balances or product sales rankings: no tool on this server provides them. For invoice counts or the tax-inclusive invoiced (sales) value, use myob_get_sales_invoice_totals. </do_not_use_for> <hints> - If the user does not specify a period, or uses vague yearly phrasing ("this year", "the year", "over the year", "recently"), omit both date parameters; the server defaults to the current financial year start through today. Never ask the user to clarify the period. - Yearly phrasing ("this year", "last year", "past year") and a plain year ("2025") mean the business FINANCIAL year, not the calendar year. Only an explicit calendar reference ("calendar 2025", "calendar year", "on a calendar year basis", "January to December") means January 1 to December 31 of that year. - A quarter ("this quarter", "last quarter", "Q1 2026", "Q3") means a FINANCIAL-year quarter, not a calendar quarter, unless the user says calendar. Call myob_get_financial_year_dates and resolve it from the returned fy_quarters_start, which gives the financial-year quarter start months. - In "Qn YYYY", YYYY names the FINANCIAL year, matching the FY labels returned by myob_get_financial_year_dates (an FY is named by the year it ENDS). So with a June financial year end, Q1 2026 is the quarter beginning July 2025, inside FY2026 (July 2025 to June 2026). - If the user asks about financial dates (financial year, fiscal year, FY, FYTD), call myob_get_financial_year_dates to get the financial year dates, then pass them here. - For an in-progress period, pass today or omit to_date; any end date after today (including current_fy.end of the financial year in progress) is capped at today, so a full-FY request for the current year returns year to date, not the future FY end. - Leave is_cash_basis false (accrual) unless the user explicitly asks for cash accounting (e.g. "cash basis", "cash accounting", "on a cash basis"). - Never invent dates or periods the user did not state. - Set include_children=true for account-level questions and read the matching account from the section's children; if it is not there, report it as not found; do not retry with alternate spellings or substitute a related account. - Always state the resolved period in your answer. </hints> <examples> - "Are we more profitable than this time last year?" - "What percentage of revenue goes to cost of sales?" - "How much electricity did I pay last year?" (include_children=true) - "What are my top expenses over the year?" (include_children=true) </examples> Sections typically include Income, Cost of Sales, Gross Profit, Expenses, Operating Profit, Other Income, Other Expenses, Net Profit. Do not assume this order. Structurally unsafe section or account labels are replaced with the quarantine marker. Returns a dict with these top-level fields: breakdown: The breakdown granularity applied (TOTAL/MONTH/QUARTER/YEAR). accounting_method: "Cash" or "Accrual". period: "from_date to to_date" string. Present only when breakdown=TOTAL. period_defaulted: True. Present only when the server supplied one or both dates because they were omitted, or capped a future end date at today. sections: Ordered list with one entry per top-level P&L section. Each section entry contains: row: Section name (e.g. "Income", "Net Profit"), or the quarantine marker when structurally unsafe. total: Aggregate dollar value for the section across the requested period. periods: Dict of {period_label: amount} keyed by a Platform-controlled, whitespace-trimmed period label. Present only when breakdown != TOTAL. A None value means no data was recorded for that period. children: Individual accounts under the section (only when include_children=true and the section has accounts), flattened to leaf accounts and sorted by absolute total descending. Each child has a quarantined name, total, periods (non-null periods only, when breakdown != TOTAL), and, when the API supplies prior-year data, prior_year_total, variance_dollars, variance_percentage. Children carry no per-period prior-year or variance dicts. Prior-year comparison fields per section (omitted when the API has no prior-year data for that section): prior_year_total: Section total for the equivalent period one year earlier. variance_dollars: total minus prior_year_total (current vs prior year). variance_percentage: variance_dollars expressed as a % of prior_year_total. prior_year_periods: Per-period prior-year amounts. Present only when breakdown != TOTAL. variance_dollars_periods: Per-period dollar variance vs prior year. Present only when breakdown != TOTAL. variance_percentage_periods: Per-period % variance vs prior year. Present only when breakdown != TOTAL. Totals and variances come from the API where provided (a missing section total is summed from that section's non-null period values). Report values as returned; do not recompute them. Does not return: invoice-level or transaction detail, cash balances, or any data for another business. Invalid dates, dates outside the last 3 financial years, invalid breakdown, or retrieval failures raise a tool error.

myob_get_profit_loss

Use this when the user asks how many invoices or the total sales billed. Reports invoice count, total invoiced (sales) value, and balance due for a period. Counts and totals cover invoices *issued* within date_from..date_to; an older invoice that is still unpaid is not included. Credit notes are excluded from every total. Only data for the last 3 financial years can be returned. <do_not_use_for> Revenue or income figures: total_amount is the tax-inclusive invoiced value, not accounting revenue; use myob_get_profit_loss. Invoice-level detail or customer collection risk (myob_get_outstanding_customer_balances). </do_not_use_for> <hints> - If the user does not specify a period, or uses vague yearly phrasing ("this year", "the year", "over the year", "recently"), omit both date parameters; the server defaults to the current financial year start through today. Never ask the user to clarify the period. - Yearly phrasing ("this year", "last year", "past year") and a plain year ("2025") mean the business FINANCIAL year, not the calendar year. Only an explicit calendar reference ("calendar 2025", "calendar year", "on a calendar year basis", "January to December") means January 1 to December 31 of that year. - A quarter ("this quarter", "last quarter", "Q1 2026", "Q3") means a FINANCIAL-year quarter, not a calendar quarter, unless the user says calendar. Call myob_get_financial_year_dates and resolve it from the returned fy_quarters_start, which gives the financial-year quarter start months. - In "Qn YYYY", YYYY names the FINANCIAL year, matching the FY labels returned by myob_get_financial_year_dates (an FY is named by the year it ENDS). So with a June financial year end, Q1 2026 is the quarter beginning July 2025, inside FY2026 (July 2025 to June 2026). - If the user asks about financial dates (financial year, fiscal year, FY, FYTD), call myob_get_financial_year_dates to get the financial year dates, then pass them here. - For an in-progress period, pass today or omit date_to; any end date after today (including current_fy.end of the financial year in progress) is capped at today, so a full-FY request for the current year returns year to date, not the future FY end. - Never invent dates or periods the user did not state. - Always state the resolved period in your answer. </hints> <examples> - "How many invoices did we raise last quarter?" - "What was our total invoiced value for the year?" - "How many invoices did we issue this financial year?" </examples> Returns a dict with these fields: total_count: Number of invoices issued in the period. total_amount: Sum of all invoice amounts (including tax). total_balance_due: Outstanding balance across those invoices. total_overdue: Overdue balance across those invoices, measured as of today, not as of date_to. period: "date_from to date_to" string representing the queried range. period_defaulted: True. Present only when the server supplied one or both dates because they were omitted, or capped a future end date at today. Does not return: individual invoice records, or the business's whole receivables position (use myob_get_outstanding_customer_balances). Invalid dates, dates outside the last 3 financial years, or retrieval failures raise a tool error.

myob_get_sales_invoice_totals

Use this when the user asks about the standard or default payment terms. Reports the business's standard, business-wide configured payment terms (for example how many days customers have to pay an invoice). Takes no arguments; it reads from the business's configured sales settings. <do_not_use_for> A specific customer's terms (those appear only in myob_get_outstanding_customer_balances, and only for customers with unpaid invoices) or overdue balances (myob_get_outstanding_customer_balances). </do_not_use_for> <examples> - "What are our payment terms?" - "How long do customers have to pay?" </examples> Returns a dict with these fields: payment_type: The validated PaymentType value from Sales Settings (e.g. "InAGivenNumberOfDays" or "CashOnDelivery"). number_of_days: The configured number of days for balance due (e.g. 14, 30). description: A human-readable summary of the payment terms (e.g. "14 days from invoice date"). Retrieval failures raise a tool error.

myob_get_standard_payment_terms