Integrations
SAP Integration
Documents in, SAP postings out: how the connection works and what gets confirmed before go-live.
What moves
What flows between SAP and PTAS AI
Documents and master data come in. Posted supplier invoices, attachments and payment status go out. In an SAP integration, AI does the reading and the matching; SAP stays the system of record.
SAP S/4HANA or ECC
The documents
Your configuration
PTAS AI
Supplier invoices posted, not keyed
One supplier invoice per document, lines matched to the purchase order and goods receipt, the image attached, posted only after approval.
Payment status back in the queue
The clearing document and payment date come back from the payment run, so FinSuite knows what was paid without anyone looking it up.
A trail on both sides
The SAP document number sits on the invoice record in FinSuite; the invoice image sits on the SAP document.
SAP is a planning example here, not a packaged connector. Whether your instance is S/4HANA or ECC, which interfaces your basis team will release and who approves what are confirmed during assessment.
How FinSuite posts to a ledgerIntegration methods
How SAP can be connected
Four ways in. Which one fits depends less on SAP itself than on your basis team, your support contract and how your SAP is run.
Native
What SAP ships itself
SAP sells its own invoice management options and some S/4HANA customers run them. We install nothing inside SAP, and nothing here is a packaged connector or an SAP Store listing. The connection is built outside SAP, around your systems.
API
OData on S/4HANA, BAPIs over RFC on ECC
S/4HANA releases OData APIs for the business partner, purchase order and supplier invoice. ECC takes the same reads and postings through standard BAPIs called over RFC. One technical user, authorised for those calls and nothing broader. Our default for both.
File
IDoc and flat files
An inbound INVOIC IDoc through a port your basis team already monitors, or a flat file on SFTP loaded on a schedule. Slower than an API, and sometimes the only route an outsourced support contract allows. Status comes back the same way.
Custom
Integration Suite on BTP, or several systems
Groups already on SAP Integration Suite on BTP usually route the traffic through it, so monitoring stays in one place. An ECC entity beside an S/4HANA one, or SAP as one of three systems in the flow, needs orchestration on top: one queue, one policy, one mapping per company code.
Our default for S/4HANA is API integration through the OData APIs SAP releases, called by a technical user your basis team scopes. On ECC the same work goes through standard BAPIs over RFC. Where an outsourced partner runs your SAP, or the basis team will not open a direct route, an IDoc or a flat file on a schedule does the same job a few hours later and is usually easier to get approved. All of them use interfaces SAP ships.
Field mapping
Where each finance object lands in SAP
The mapping is agreed before build and kept per company code, in the terms your SAP team already uses. This is the starting point we bring to the assessment.
The entry, on both sides · Illustrative example
Field mapping is yours to define. Entries are validated against it before they reach the ERP, not rejected by it afterwards.
Security of the connection
What protects the link to your SAP system
Four controls, each one visible to your basis and security teams. None of them depends on trusting us.
A technical user your basis team creates
The connection signs in as a system user authorised for the services it calls and nothing broader. Credentials are stored encrypted and rotated on your schedule, and the user can be locked in SAP at any time.
Inside your network boundary
An on-premise SAP stays behind your firewall. Traffic arrives by the route your security team approves: a VPN, an allow-listed address, or Integration Suite on BTP. On-premise or air-gapped deployment is available where supported.
Every call logged with its evidence
Each read and posting is recorded with the document it came from, who approved it and the SAP document number returned. A failed posting is kept with the message SAP gave and goes to a person, not into a retry loop.
Quality system first
The mapping is built and tested against your quality system with a copy of your master data and tolerances, and moves to production through your change control after your finance team has seen the postings.
FAQ
Questions SAP teams ask
Do you work with ECC, or only S/4HANA?
Both. S/4HANA has released OData APIs, so the link can be direct and close to real time. ECC takes the same postings through BAPIs over RFC, or an IDoc where your basis team prefers a port it already monitors. If a move to S/4HANA is on the roadmap, say so at assessment, and the mapping is planned around the business partner conversion.
Will invoices appear in SAP before they are approved?
Only if you want them to. SAP can park a supplier invoice before it posts, and some finance teams run approval on parked documents inside SAP; then we park a complete document and leave approval there. Otherwise FinSuite holds the invoice until the right person approves it, then posts. One place approves, never both.
We have eleven company codes across two instances. Is that eleven integrations?
One integration, one mapping per company code. Each code has its own tax codes, tolerances and reconciliation accounts, so the mapping is kept per code, and ECC and S/4HANA are connected by different methods. The queue is shared, with company code as a dimension, so one team can work all eleven.
Is this an add-on inside SAP, or something on SAP Store?
No. We do not claim an SAP certification, a partnership or a listing on SAP Store, and we would rather say so here than let a slide imply it. The connection is built outside SAP against interfaces your basis team releases, and your team can see every call it makes.
Keep reading
Related integrations
Oracle Integration
Fusion Cloud ERP and E-Business Suite, by REST API or file load, with status written back.
Read more →Microsoft Dynamics Integration
Finance & Operations and Business Central through OData, data entities and Dataverse.
Read more →FinSuite Integrations
The four integration methods and how FinSuite posts into any ledger.
Read more →All integrations
ERPs, accounting suites, the REST API and webhooks in one list.
Read more →Next step
Bring a month of supplier invoices and your tolerance settings
An assessment starts with your real documents and your quality system, never production. Nothing posts until your finance team has seen the entries.