Sage reported a Sage Intacct partial outage on September 24, 2026, after customers began having trouble exporting financial reports to Excel. The company said it had identified a global issue affecting that export workflow, while other product functionality continued to operate.
That kind of partial outage can be easy to underestimate. The accounting system may still open. Users may still log in. Transactions may still be visible. But if the exact report a controller, bookkeeper, lender, board, grant manager, or owner needs cannot be exported at the right moment, the business still has an operational problem.
The risk is the workflow, not just the application
Cloud accounting platforms are now part of the operating system of many small and midsize businesses. Sage Intacct, QuickBooks, NetSuite, Xero, payroll portals, banking feeds, expense tools, and reporting add-ons often work together to produce the numbers that guide cash, staffing, purchasing, job costing, and compliance decisions.
A SaaS partial outage is different from a full outage because it can hide in one narrow workflow. A team may only discover the problem when a month-end export fails, a board packet is due, a lender asks for updated financials, or a manager needs a spreadsheet to reconcile a variance. The cloud is still there. The report is not.
For New Jersey business owners and operators, the decision is not whether to panic over one vendor incident. It is whether reporting workflows have enough continuity planning for the work the business actually depends on.
What owners should ask
This is a good moment to review whether finance and operations teams know what to do when a cloud accounting workflow stalls. The most useful questions are practical:
- Which reports are deadline-critical? Identify the exports that support payroll, cash-flow reviews, lender reporting, board meetings, grants, tax work, job costing, or customer billing.
- Who watches vendor status pages? Decide whether finance, internal IT, the MSP, or the software administrator is responsible for checking and documenting vendor updates during an incident.
- What workaround is acceptable? A vendor workaround may be fine for some reports and unacceptable for others. Decide that before the deadline pressure starts.
- How current are cached reports? Some businesses should keep scheduled exports or read-only snapshots of key financial reports so a temporary export issue does not leave everyone empty-handed.
- When does the issue get escalated? Set a threshold for when a software ticket becomes an owner-level business decision because a reporting deadline, payment decision, or compliance obligation is at risk.
Partial outages deserve full ownership
The common mistake is treating a partial outage as someone else's inconvenience. Finance may assume IT has it covered. IT may assume the software vendor has it covered. The MSP may not know the report exists. The vendor may publish a workaround, but no one inside the business may know whether that workaround satisfies the reporting requirement.
That leaves the business with a familiar gap: everyone owns a piece of the tool, but no one owns the end-to-end workflow. Accounting software continuity should name the business process, the deadline, the owner, the fallback, and the point of escalation.
This does not require a giant binder or a dramatic disaster recovery project. Start with the handful of reports that would cause real pain if they were unavailable for a day. Document where they come from, who can run them, whether they can be exported on a schedule, and what the team does when the export path fails.
A practical next step
Ask your finance lead, software administrator, and IT provider to pick three critical reports and walk through a simple failure scenario: the system is online, but the report export does not work. Can the team still get a usable number? Can someone prove when the vendor incident started? Is there a workaround? Who tells leadership if the workaround is not good enough?
If the answer is fuzzy, the fix may be simple: scheduled exports, documented alternate report views, clearer software support contacts, a vendor-status monitoring habit, or a short escalation checklist. The point is not to build a perfect backup for every screen. It is to make sure a cloud accounting partial outage does not become a full stop for the business decision that depends on the numbers.
Sources and further reading
