Loading

Capita Integra

The Capita Integra connector links ActiveManage with Integra 2 (Integra Financials) and Integra Centros in both directions: transactions extracted from Integra come into the feed queue, and postings made here can be mirrored out to Integra while it remains a site's statutory book. It is built for public-sector sites that run operations on ActiveManage but must keep Integra for some years. It has not yet been run against a real Integra system, so treat the first connection as a project, not a switch.

Where to find it

Admin Panel → Finance:

  • Bank Feeds & Reconciliation — the Connections tab (Integra connections and settings), the Queue tab (what came in) and the Outbox tab (what went out)

Architect Panel → ERP - Finance:

  • Feed Queue — the same console, where an architect switches the Integra providers on
  • Accounting Code Map — your codes against Integra's

The two providers

  • Capita Integra 2: customer-hosted with SQL Server behind it. Reached through its SQL interface tables by default, or by file exchange.
  • Capita Integra Centros: hosted by Capita. Reached through its API by default, or by file exchange.

Both ship switched off with no credentials. Nothing about Integra's interface is fixed in the product: endpoint paths, interface table and column names, and file layouts are all settings, because each site's Integra is configured differently.

Setting up a connection

  1. An architect switches the provider on under Providers (site-wide) and enters what is true for the whole Integra system, such as its service address and credentials.
  2. Create a connection per company and ledger with New bank / feed connection, choosing the Integra provider. A site reading both its general ledger and its purchase ledger runs two connections.
  3. Open the connection's Settings and set Transport to file, sql or api. For sql give the Database server, Database name, Database user and Database password; for api the Service address, App client ID, App client secret or API key; for file the inbound, outbound and archive folders (an architect sets folders, inside the server's ERP drop-folder root) and the Date format.
  4. Add any further settings the site needs with New setting name and New setting value; values written as JSON are stored as structured settings. The column mappings in and out are set this way.
  5. Map codes in Accounting Code Map.
  6. Press Sync now and check the first lines on the Queue tab: amounts signed the wrong way round are the first thing to look for.

Inbound

Extracted lines land in the feed queue uncoded, like any bank line, and are coded by your rules or by a person. Integra's own coding travels with the line but is never trusted into the coding: a narrative that says "post this to 4000" is text, not an instruction. Unmapped codes are fine inbound.

Outbound

Outbound uses the generic outbound mirror (see the outbound mirror article in this section), switched on per connection. Unmapped accounts are refused. Writing into Integra 2's interface tables is refused unless the tables are named in an allow-list setting, because a direct write bypasses Integra's own validation, period control and audit. Payments are not mirrored to Integra.

File transfer by SFTP

Integra file pickup can fetch files from an SFTP server into the inbound folder first. This needs the SSH extension on the web server, has not been verified against a live server, and refuses an SFTP-only account (one that may not run commands) with a message saying so.

What goes wrong

  • Every amount is backwards: the site's extract signs amounts the other way. Correct the sign setting before coding anything.
  • Dates a month out: set the Date format, for example d/m/Y.
  • Sync now refuses a folder: the folder does not exist or is outside the server's ERP drop-folder root. The message names the setting; ask an architect to correct it.

Worked example

A council runs purchasing on ActiveManage but files from Integra 2. The architect switches on Capita Integra 2; the finance lead creates a GL connection with the file transport, pointing at folders the platform administrator created, and maps 120 nominal codes. Mirroring is switched on from 1 April. After a week of comparing the first journals in Integra with the originals, the Accounting Outbound Mirror task is enabled.

Recommendations

  • Start with the file transport; it is the only one exercised end to end.
  • Agree interface details with the site's Integra consultant before entering settings.
  • Keep inbound and outbound separate decisions: a site keeping Integra as book of record may run outbound only.
  • Check the first documents in Integra by hand before relying on the mirror.