Connect Paige to SAP Business One
Two working paths from Paige into SAP Business One: the Data Transfer Workbench to load a batch of A/P invoices from Paige's CSV, or an integration with the Service Layer that creates each A/P invoice and attaches the PDF. Which to pick, what lands in SAP B1, and the step-by-step guides.
Administrators5 minutes to chooseVerified 2026-09-05
Paige reads the invoice — vendor, invoice number, dates, total, even handwritten ones — and SAP Business One gets the A/P invoice, with the PDF attached, without anyone keying it in.
SAP Business One (SAP B1, "SAP" at most small and mid-size companies that run it) loads data two ways from outside: the Data Transfer Workbench (DTW) for files, and the Service Layer API for integrations. Paige's export feeds either.
What lands in SAP Business One
| Data Transfer Workbench | Service Layer integration | |
|---|---|---|
| An A/P invoice per invoice | Created when you run the import, in batches | Created minutes after Paige finishes the invoice |
| Vendor, dates, vendor reference, service line account and amount | From Paige's CSV via DTW's Documents and Document_Lines templates | From Paige's fields |
| The PDF attached | No — attach by hand on the invoice's Attachments tab | Yes — uploaded to Attachments2 and linked on the invoice |
| Who does it | An SAP B1 administrator or key user | A developer |
Pick a path
| Path | Choose it when | Guide |
|---|---|---|
| Data Transfer Workbench | You already use DTW and can attach PDFs by hand, or don't need them attached. | Import Paige invoices into SAP Business One with the Data Transfer Workbench |
| Service Layer | You want invoices to appear on their own with the PDF attached. | Integrate Paige with the SAP Business One Service Layer |