Twenty-plus years living in Saturn as the daily source of truth — writing the MaxBasic, designing the forms, owning the reporting. XBA makes Accredo do the specific things your business does, without compromising the ledger it runs on.
Personal reply from Andrew within one business day.
Accredo Saturn is deeply extensible if you know where the hooks are. This is the toolbox — each capability delivered as a documented, supportable build, not a one-off script.
Business rules enforced where they belong — in the transaction itself. BeforeSave validation, AfterSave and AfterPost automation, OnPrint document logic, plus scheduled batch scripts for the work that runs overnight.
Custom entry screens, dashboards and maintenance forms built in Saturn's Form Designer — grids, combos, live lookups and code behind them. Invoices, packing slips and statements that print exactly what your process needs.
Standalone custom tables and extension fields on Accredo's own tables, indexed and registered properly — so the data your business actually runs on lives inside Saturn with everything else, not in a spreadsheet beside it.
SP scripts that resolve multi-tier customer agreements, contract pricing and volume breaks at quote and invoice time — automatically, consistently, and without the sales team maintaining a shadow spreadsheet.
Saturn's web service API opens the ledger to the systems around it — reads, standard record writes and raw queries over OData/REST. The route for connecting web apps, Microsoft 365, HubSpot, e-commerce and reporting tools.
From reports inside Saturn to live browser dashboards reading ERP data — branch performance, stock, pricing and margin in one view that refreshes itself, instead of a monthly spreadsheet ritual.
The most expensive gap in most Accredo sites isn't in the office — it's everywhere the work happens away from a Saturn terminal. Goods received in the warehouse, jobs completed in the field, returns arriving at the dock: all captured on paper or memory, then re-keyed later, with drift.
XBA builds web applications for exactly these edges — barcode-driven warehouse capture, field service job sheets, returns processing — that capture the record once, at the source, and post it to Saturn the way Saturn posts to itself. The flagship field-service build on the homepage work section is one of them.
Getting data into Saturn safely is a design decision, not a default. Reads and standard records travel the supported OData API. Transactional writes that have to land cleanly use native MaxBasic, posting directly the way Saturn posts to itself. Both routes treat the ledger as the single source of truth.
// The wrong path is how integrations corrupt ledgers. Choosing correctly is the specialty.
Running Accredo Saturn and drowning in a manual process? Tell me what's eating the week — the audit is free.
Book a free process audit