Marketplace Settlement Reconciliation and Month-End Close, Automated

BATI CIS is a B2B middleware that collects order, shipment and settlement data from global commerce channels such as Amazon, Shopee and TikTok Shop, builds daily sales from actual shipments, reconciles them with incoming settlements every day, and posts journal entries to SAP or your ERP. It covers the OMS side of collecting order and shipment data together with settlement and sales management; it does not create fulfillment orders or handle delivery.

BATI CIS is used by operations, finance, business management, and ERP teams at global e-commerce brands that sell across multiple marketplaces.

Yes. BATI CIS standardizes raw commerce data and transfers only the required data to SAP or internal ERP systems as middleware.

As of November 2026, BATI CIS processes customer data every day from 11 overseas platforms (34 country marketplaces) and 16 Korean channels. Overseas: Amazon, Shopee, TikTok Shop, Walmart, Qoo10, Rakuten, ZOZOTOWN, Tmall, Douyin, Shopify and SHOPLINE. Korea: Naver SmartStore, Coupang, Kakao Shopping, Lotte ON, CJ Onstyle, Musinsa, Zigzag, Ably, Cafe24 and others. Collection is set per channel, automatic or by receiving files, and the scope for each channel is confirmed in the consultation.

From collecting settlement reports to ERP journal entries. Each channel's settlement report is matched against order and sales data (settlement reconciliation), fees and net sales are organized by channel and product, and the result goes to your ERP as journal entries in the format it accepts. For channels that use two-step verification, collection is adjusted: BATI CIS receives files instead of collecting automatically.

Yes. BATI CIS takes shipment and return data from 3PLs and fulfillment centers and matches it with channel orders and settlements. Orders that have not shipped yet and items that came back are kept apart, so sales and settlements follow what actually shipped and returned.

In the published customer case (a K-beauty brand with about KRW 500B in annual revenue), the finance team cut month-end close from 3 days to 3 hours. Results depend on the number of channels and data volume.

Yes. SAP has a public case, and Douzone, Younglimwon, ECOUNT and Oracle can also be connected, with sales and settlement data sent as journal entries in the format each ERP expects. For in-house ERPs, the integration is designed together.

Accounting software and ERPs handle what happens after a journal entry exists. BATI CIS handles the step before: collecting raw data from many sales channels, standardizing it, reconciling settlements and turning the result into entries. Your ERP stays as it is.

Install the Cafe24 app and open it with [Manage] in the Cafe24 admin: your store and SmartStore sales appear by date in one table, with Excel download. Free during the beta.

Multichannel order management tools (OMS) cover operations such as order collection, shipping labels and inventory; accounting software and ERPs cover the finance work after entries exist. Matching channel settlements to actual shipments and returns sits between the two and usually stays in spreadsheets. BATI CIS runs the operations data (orders, shipments) and the finance data (settlements, close, entries) in one system.

It does not create fulfillment orders or handle delivery. It does not replace the ERP; it prepares journal entries in front of it. For channels that use two-step verification it receives files instead of collecting automatically. How to handle mismatches found in reconciliation is the finance team's decision. The scope for each channel is confirmed in the consultation before work starts.