Integrating Access Attaché with a B2B ordering platform: what actually syncs

Access Attaché Accounts — still widely called "Attaché" by the NZ and Australian businesses that have run it for years — is a fixture of mid-market accounting across the region. It handles general ledger, accounts receivable and payable, payroll with NZ payday filing compliance, multi-company and multi-branch setups. For businesses that chose it a decade ago and have their financial data structured around it, it continues to do that accounting work well.

The challenge isn't the accounting. It's everything around it. Distributors and wholesalers running Attaché typically need it connected to a B2B ordering portal, an inventory system, a warehouse operation, or all three. Customers placing orders online need to see their correct pricing. Invoices need to land in Attaché automatically. Stock levels displayed in the portal need to reflect what's actually in the warehouse.

Getting those data flows working reliably is where most Attaché integration projects run into trouble — not because the goal is unreasonable, but because Attaché's integration model is different from the cloud-native tools that most portal platforms assume.

Why Attaché integration is different

Attaché was built as an on-premises system, and that shapes how integration works. Where a cloud-native platform like Xero exposes a well-documented REST API with OAuth authentication and webhook events, Attaché's integration story is more varied: structured file exchange, direct database reads in some configurations, and in more recent versions under The Access Group, additional connector options.

This isn't a criticism of the software — it's a practical reality to account for in an integration design. A B2B portal that was built assuming REST-API availability needs a translation layer between its data model and Attaché's. That layer needs to be reliable, monitored, and able to recover gracefully when the connection drops.

Businesses that approach Attaché integration expecting a quick plug-in connector usually find that the connector works for basic product data but breaks down on pricing — which is exactly where accuracy matters most.

The seven data flows that need to sync

A complete Attaché integration for a distributor running a B2B portal covers these data flows:

1. Customer / debtor records

Attaché stores customers as debtors, with account codes, credit terms, GST treatment, and contact details. These need to be mirrored in the portal so that a customer logging in sees their account — not a generic guest view. Changes in Attaché (new customer, credit limit change, account suspended) need to flow to the portal. The sync direction here is primarily Attaché → portal, with new customers occasionally flowing back the other way if the portal is the first system they enter.

2. Product catalogue and SKUs

Product records in Attaché — codes, descriptions, units of measure, GST status, barcode — need to feed the portal's product listings. This is typically the most straightforward part of the integration once the initial sync is running, provided product codes are consistent and SKUs don't change frequently.

3. Customer-specific pricing

This is the hard one. See below.

4. Inventory / stock levels

If Attaché is the inventory system of record, stock-on-hand quantities need to push to the portal so customers can see availability before ordering. The frequency of this sync determines how often you oversell a product that's actually out of stock — an operational and customer-experience problem.

5. Inbound orders (portal → Attaché)

When a customer places an order through the portal, that order needs to create a sales order in Attaché — correctly coded to the right debtor account, with the right pricing, freight treatment, and delivery address. Errors here create fulfilment problems and accounts-team rework.

6. Invoice generation and delivery

Once an order is fulfilled, Attaché generates the invoice. That invoice needs to be visible in the customer's portal account, downloadable as PDF, and ideally triggers an email notification. Customers who can't find their invoices online call your accounts team — which defeats the purpose of self-service ordering.

7. Payment status

Where customers pay online through the portal, those payments need to be reconciled against the outstanding debtor balance in Attaché. Where customers pay by EFT or cheque in the usual way, the portal should reflect updated account balances and overdue status so credit limits are applied correctly.

The pricing complexity problem

Customer-specific pricing is a defining feature of Attaché for distributors. Most distributors running it have layered pricing structures built up over years: base price lists, customer price codes, quantity break tiers, and contract prices negotiated individually with key accounts. Some customers have dozens of products with individually negotiated prices that don't fit any standard price list.

Surfacing the correct price for a specific customer on a specific product in a B2B portal requires the integration to:

• Extract the full pricing structure from Attaché — not just the default price list
• Map Attaché price codes to portal customer profiles correctly
• Resolve the right price at query time, applying the correct quantity break if the customer is ordering a larger quantity
• Keep this current as Attaché pricing changes — a price update that doesn't flow to the portal results in customers seeing the wrong price and orders being placed at incorrect values

Integrations that handle basic product data but skip the pricing layer tend to result in one of two outcomes: portals that show a single generic price list to all customers (rendering the whole point of a B2B account login meaningless), or portals that require staff to manually review and reprice every order before it goes to Attaché (which is just an expensive re-keying exercise wearing a portal costume).

Technical approaches to Attaché integration

Three main architectures appear in practice:

File-based exchange is the most common approach for existing Attaché installations. Attaché exports structured files on a schedule — CSV or XML — which the integration layer picks up, transforms, and pushes to the portal. Data flows back from the portal via files that Attaché imports on its own schedule. The tradeoff is latency: sync cycles typically run every fifteen to thirty minutes, which is acceptable for most distributors but creates a window where the portal and Attaché are out of step.

Database-level reads allow a connector to read directly from Attaché's underlying database in a read-only capacity, enabling more frequent sync without relying on Attaché's export schedule. This approach gives better data freshness, but requires careful implementation to avoid impacting Attaché's performance and needs to account for schema changes when Attaché updates.

Connector and middleware options have expanded under The Access Group's ownership of Attaché. Where available, these provide a more structured integration surface. The appropriate approach depends on your version of Attaché, your hosting environment (on-premises, managed server, or Access-hosted cloud), and the data volumes involved.

In practice, most production Attaché integrations use a combination — file-based for the high-volume data like product catalogues and stock, with direct or connector-based reads for pricing and account status where accuracy matters most.

Resilience: what happens when the connection drops

On-premises Attaché instances get taken offline for updates, backups, and maintenance. A well-built integration handles this gracefully: the portal continues to serve customers from a cached data set, queues any orders placed during the outage, and processes them into Attaché once the connection is restored. An integration without this queuing layer either shows customers errors during Attaché downtime, or loses orders that were placed while the connection was down.

Monitoring matters too. File-based integrations that silently stop pushing are a common failure mode — the files stop arriving and nobody notices until a customer complains that their pricing hasn't updated or their order didn't make it through. Alerting on missed sync cycles is a basic operational requirement, not an optional extra.

When Attaché integration isn't enough

Some businesses reach a point where the overhead of maintaining the Attaché integration — working around its scheduling constraints, managing the pricing sync complexity, keeping the translation layer current through Attaché updates — exceeds the value of keeping Attaché as the financial system. That's often the same moment when the B2B ordering operation has grown large enough that it needs features the portal alone can't provide: full warehouse management, integrated purchasing, or real-time multi-branch inventory.

At that point, the conversation typically shifts from "how do we integrate better with Attaché" to "what does it look like to build a custom ERP that owns the whole data model." That's a bigger decision — but for businesses running high volumes through a distributor operation, owning the full stack often costs less over five years than maintaining a patchwork of integrations between systems that were never designed to work together. The replace-vs-integrate decision framework is worth working through before committing either way.

What this looks like in practice

When Zeabyte integrates Attaché with a B2B ordering platform or a custom distribution platform, we treat pricing as the hardest problem and solve it first — building the extraction and mapping logic for Attaché's price codes and quantity breaks before we write a line of portal code. We run the full data flow through a staging environment with real Attaché data before anything goes near production, and we build monitoring into the integration from the start rather than bolting it on after the first time something goes quietly wrong.

Attaché is one of the systems we connect in production alongside Accredo, MYOB, Xero, CSB-System and others — see the full integrations list. If your business runs on Attaché and you need it talking to an ordering or distribution platform, talk to us — we can scope exactly what the integration involves before you commit to anything.