Skip to main content
SAP integration

SAP e-commerce integration: marketplace orders and settlements as SAP journal entries

BATI CIS collects order, shipment, sales and settlement data from marketplaces such as Amazon, Shopee and TikTok Shop and from your 3PLs, standardizes it, and reconciles each channel's settlements against actual shipments and returns. It then builds journal entries in the format SAP expects and sends only the data SAP needs, so your SAP stays as it is.

What happens when raw channel data goes straight into SAP

Every marketplace has its own order and settlement report formats. Connecting those raw files directly to SAP adds load in development, processing and month-end close.

Every channel is a separate build

Connecting channels inside SAP means one integration project per channel. Open TikTok Shop after Shopee and you build the same thing again.

Every raw record lands in SAP

Passing orders, shipments, returns and settlements line by line means SAP processes more records with every new channel and every extra order.

SAP processing cost follows the record count

Processing in SAP is expensive per record. Handling unorganized raw data there costs accordingly.

Order-based sales drift from what really shipped

Order data mixes in cancellations, returns and unshipped orders. If settlements are not matched against 3PL shipments and returns first, someone hunts for the differences by hand at every close.

BATI CIS handles channel integration outside SAP, in one middleware layer. A BATI CIS build takes 3 to 6 months and costs under KRW 300 million (standard setup; may vary with integration scope).

What BATI CIS does in front of SAP

SAP handles accounting once an entry exists. Turning scattered channel data into entries is the step before, and that is BATI CIS's job.

Channels we can connect
  • Amazon
  • Shopee
  • TikTok Shop
  • Rakuten
  • Qoo10
  • Naver SmartStore
  • Cafe24
  • Coupang
  • and more

Collection is set per channel: automatic, or by receiving files.

3PL · fulfillment

Actual shipments and returns

BATI CIS

Collect · standardize · reconcile · build entries

SAP

Journal entries

  1. 1

    Collect

    Orders, shipments, sales and settlements from each channel, plus actual shipment and return data from 3PL and fulfillment partners, come in automatically. For channels that use two-step verification, collection is adjusted: BATI CIS receives files instead of collecting automatically.

  2. 2

    Standardize

    Each channel's order and settlement report formats are converted into one schema.

  3. 3

    Reconcile settlements

    Channel settlements are matched against actual shipments and returns. Orders that have not shipped and items that came back are kept apart, and mismatches surface before the close.

  4. 4

    Journal entries

    Fees and net sales are organized by channel and product and turned into journal entries in the format SAP expects.

  5. 5

    Send to SAP

    Raw data is processed in BATI CIS, and SAP receives only the consolidated data.

Curious how settlements are matched to orders and actual shipments and returns? More on settlement reconciliation

How each channel's settlement differs: Amazon settlement · Shopee settlement

SAP environments and integration methods

SAP ECC and SAP S/4HANA run live at customers, and the SAP S/4HANA Cloud Public Edition integration is in development for a 2026 opening (as of November 2026). The method is chosen to fit each customer's SAP environment and IT policy.

SAP environmentScope
SAP ECC(SAP ERP 6.0)Sales, return and settlement entries
SAP S/4HANASales, return and settlement entries
SAP S/4HANA Cloud Public Edition(public cloud)Sales order → delivery → billing

Integration methods

File interface (SFTP)

Journal entry files in an agreed format go over SFTP. Columns and format are checked first, and a file that does not match is rejected as a whole, so nothing is posted halfway.

Cloud Integration in SAP Integration Suite (often called CPI)

Entries go by API. The document type is set automatically, and the same entry is never posted twice.

OData API (S/4HANA Cloud Public Edition)

SAP's published sales order, delivery and billing APIs, in that order.

Data exchanged

Sent to SAP
Sales, return, adjustment, cost and carry-over entries
Received from SAP
Material, customer and price master data, and sales results

Only confirmed entries go to SAP.

Rollout steps, system layout and scope are in the SAP integration guide (in Korean). Request the SAP integration guide

Published customer case

K-Beauty Brand C: BATI CIS in front of SAP, month-end close from 3 days to 3 hours

A global K-beauty brand with annual revenue around KRW 500 billion. To connect Amazon, Shopee and TikTok Shop to SAP, SAP is the ERP and BATI CIS is the middleware in between.

Finance team month-end close
3 days → 3 hours

Raw data was organized and aggregated in BATI CIS, and only the consolidated data went to SAP, so SAP, where each record is expensive to process, handled fewer records.

* Results vary by setup.

You can also see how the month-end close runs. More on month-end close automation

Douzone, Younglimwon, Ecount and in-house ERPs, the same way

The sequence is the same without SAP. SAP has a public case, and Douzone, Younglimwon, Ecount and Oracle can also be connected with journal entries in the format each ERP expects. For an in-house ERP we design the integration with you.

  • SAP (public case)
  • Douzone
  • Younglimwon
  • Ecount
  • Oracle
  • In-house ERP

SAP integration questions

Does it work with both SAP S/4HANA and SAP ECC?

Yes. As of November 2026 both SAP ECC and SAP S/4HANA run live at customers. Sales, return and settlement entries are sent by file interface (SFTP) or by Cloud Integration in SAP Integration Suite (often called CPI), whichever fits the customer's environment.

What about SAP S/4HANA Cloud Public Edition?

It is in development and opens in 2026. Entries go in through SAP's published sales order, delivery and billing OData APIs, in that order.

Does BATI CIS also receive data from SAP?

Yes. It receives material, customer and price master data and sales results from SAP. What it sends to SAP is sales, return, adjustment, cost and carry-over entries, and only confirmed ones.

Do we have to change our SAP setup?

BATI CIS does not replace SAP; it works next to it as middleware and sends journal entries in the format SAP expects, so you keep using SAP as you do today. Channels and scope are agreed in the consultation.

Can Amazon, Shopee and TikTok Shop settlements become SAP journal entries?

Yes. Each channel's settlement reports are collected and reconciled against actual shipments and returns, fees and net sales are organized by channel and product, and the result becomes SAP journal entries. K-Beauty Brand C in our published case also runs BATI CIS between Amazon, Shopee, TikTok Shop and SAP. Channel scope is confirmed in the consultation.

Why does SAP-side cost go down?

Because SAP processes fewer records. Raw data is organized and aggregated in BATI CIS, and SAP receives only the consolidated data. Processing in SAP is expensive per record, so fewer records mean lower cost.

Are 3PL shipment and return data reflected in the SAP entries?

Yes. Shipment and return data from 3PL and fulfillment partners is matched with channel orders and settlements. Orders that have not shipped and items that came back are kept apart, so SAP receives sales for what actually shipped.

How long does a build take and what does it cost?

A standard BATI CIS build takes 3 to 6 months and costs under KRW 300 million. It depends on the channels, logistics and ERP you connect, so the exact timeline and cost are given in the consultation.

Has it been rolled out alongside an SAP consulting firm?

Yes. K-Beauty Brand C in our published case rolled it out together with a consulting firm. SAP is their ERP, and BATI CIS is the middleware between their global channels (Amazon, Shopee, TikTok Shop) and SAP.

Related articles

Articles are in Korean.

Start by telling us your channels and monthly order volume

Enterprise builds start with the inquiry form. We scope the channels, logistics and SAP integration together, and a dedicated manager supports rollout and operations.

Smaller brands running a Cafe24 store can start right away with the Cafe24 app. About the Cafe24 app

Contact sales