July 2026 · Preliminary — open for review

AP routing connections

Two-way sync with AP routing networks, field ticketing, JIB exchanges, treasury and tax validation services.

Acting as

Connections

7 integrations · inbound documents land in AP intake

ConnectionTypeDirectionCadenceLast syncPending inboundState

Coupa AP routing

Approval chains + coding rules

AP routingBidirectionalEvery 15 minAug 06 06:154connected

OpenInvoice (Enverus)

Field service invoices & tickets

AP routingInboundHourlyAug 06 05:407connected

SAP Ariba network

Credential renewal required

AP routingInboundHourlyAug 05 18:022degraded

EnergyLink JIB exchange

Non-operated JIB packages

JIB exchangeInboundDaily 04:00Aug 06 04:103connected

WellSight field tickets

Three-way match support

Field ticketingInboundEvery 30 minAug 06 06:0212connected

Treasury ACH file transfer

NACHA payment files

BankingOutboundOn releaseAug 05 16:00—connected

1099 / W-9 validation service

TIN matching not enabled

TaxBidirectionalManualJul 28 09:44—disconnected

What each sync brings in

Mapping rules applied on arrival

  • Invoice header, lines, PO reference and vendor tax ID → AP intake with a classification score.
  • Field tickets → three-way match support (PO, ticket, invoice) before approval.
  • Approval chains and delegation-of-authority limits mirrored from the routing tool.
  • Outbound: approved invoice status, GL reference and payment date returned to the network.

Controls

Applied to every inbound document

  • Duplicate detection on vendor, invoice number, amount and service period.
  • Vendor must exist and be approved in the vendor master before an invoice can be coded.
  • Rate checks against master service agreements raise a price-variance exception.
  • Service dates outside the open accounting month are flagged for cutoff treatment.