How can enterprises in the high-end manufacturing industry implement tax control interface services?

Complete interface integration on both sides according to agreed fields; invoicing information is automatically passed in from the business system, invoices are automatically issued, and results are automatically returned; business documents correspond one-to-one with invoices, and manual transcription and backfilling are eliminated; adapt development to the customer's actual business rules, so existing processes need not be modified to accommodate the system; after integration, data on both sides syncs in real time, exceptions trigger automatic alerts, and reconciliation and traceability no longer rely on manual work.

What problems existed before COSCO Shipping Kawasaki launched input and output invoice management?

Product delivery targets include both OEMs and distribution systems, as well as scattered after-sales and spare parts customers, with invoicing needs raised separately according to batches and contract milestones; business systems and invoicing capabilities are independent of each other. After each business transaction is completed, customer information, amounts, and product details need to be manually transcribed item by item to the invoicing end, and after invoicing, the invoice number is written back to the business system; manual transcription becomes a fixed consumption as business volume grows, and transcription itself is also a source of errors.

← Back to case list

High-end manufacturingInput and Output Management

COSCO Shipping Kawasaki · Large shipbuilding enterprise

COSCO Shipping Kawasaki | Payment management system tax control interface service

Tax control interfaceService Content

Payment systemIntegration target

Enterprise overview

Nantong COSCO Shipping Kawasaki Ship Engineering Co., Ltd. is a large Sino-foreign joint venture shipbuilding enterprise held 50% each by China COSCO Shipping Group and Kawasaki Heavy Industries, Ltd. of Japan. It was established in 1995 and began production in 1999, and is known as a benchmark enterprise in China's shipbuilding industry. The company has one 300,000-ton dock and one 500,000-ton dock, equipped with 300-ton and 800-ton gantry cranes, with an annual production capacity of more than 2.5 million deadweight tons. Since its founding, it has delivered various large vessels including 20,000 TEU and 13,386 TEU container ships, 300,000-ton VLCCs, 6,200-vehicle car carriers, and 4,000-vehicle dual-fuel car carriers, and was the first in China to achieve margin-free shipbuilding, with multiple economic and technical indicators setting new Chinese shipbuilding records year after year.

Business pain points

Product delivery targets include both OEMs and distribution systems, as well as scattered after-sales and spare parts customers, with invoicing needs raised separately according to batches and contract milestones. Business systems and invoicing capabilities are independent of each other. After each business transaction is completed, customer information, amounts, and product details need to be manually transcribed item by item to the invoicing end, and after invoicing, the invoice number is written back to the business system. Manual transcription becomes a fixed consumption as business volume grows, and transcription itself is also a source of errors.
When data standards differ on the two sides, reconciliation requires manual item-by-item comparison, and problems often surface only at month-end. Personalized requirements are difficult to solve through configuration, and modifying existing business processes to accommodate generic products instead raises overall costs and implementation risks. After the rollout of fully digitalized e-invoices, invoice acquisition, issuance, and archiving all need to link with business systems, and fragmented approaches are no longer sustainable.

Solutions

Complete interface integration on both sides according to agreed fields; invoicing information is automatically passed in from the business system, invoices are automatically issued, and results are automatically returned; business documents correspond one-to-one with invoices, and manual transcription and backfilling are eliminated.
Adaptation development according to the customer's actual business rules, so existing processes do not need to be changed to accommodate the system
After integration, data on both sides is synchronized in real time, abnormalities trigger automatic alerts, and reconciliation and traceability no longer rely on manual work
Ultimately embeds invoicing capabilities into existing business workflows, allowing users to complete all operations within a familiar interface
At the same time, this integration method is accumulated as a standard, so subsequent new systems or new scenarios can be connected according to the same set of rules