Latest industry insights, tutorials, best practices and case studies.
279 articles
2024 年 Temu（拼多多海外）对账逻辑发生「**业务模式两极分化**」的剧变 ——一边是 **Temu 全托管**（商家供货 / 平台代运营代销代发货），一边是 2024 年下半年才大规模放量的 **Temu 半托管**（商家自备货到 Temu 合作海外仓 / 平台负责销售 / 商家自负责售后退货回流 / USD 结算后结汇 CNY）。两种模式对账路径**完全不一样**：全托管走二方核对（无买家订单号），半托管走「**三方两段式**」——平台账单 ↔ 海外仓入库快照 ↔ 商家内部核算 + 资金回流链独立追踪。本文以 2026-08-22 Temu 半托管试点接入定稿记录 + 试点 6 月账期实测为基准，拆透半托管对账新规则 ——核心是 **3 道闸门**（主营收入正循环 SUCCESS / 海外仓入库未映 MISSING_WAREHOUSE / 跨业务类型混淆 ORDER_TYPE_MISMATCH）+ **售后退货回流四件套**（回流单独立记账 + 货品回流登记 + 质检报废标记 + 退运费回拨）+ **USD 结算镜像**（平台收付净额 = 商家 USD 收单合计、商家实收
把电商财务的全流程拆开看，过去 18 年的"按账期对账"是"事后算账"——每月 1 次、月底拉账单、手工对账、月初出报表。2026 年的电商日均订单已是 8000-12000 单、退款潮 7-15 天、平台扣点 24 小时波动、月度差异累积 3000 万元是常态。"流程再造"不是把月对改成周对或日对——是把"以账期为单位的批量处理"重新设计为"以业务事件为单位的实时触发"：订单完成、退款完成、佣金结算、平台代扣税、ERP 推送成功 5 类事件各自触发独立流水线。本文给出 5 类业务事件的标准定义、流程再造的 3 层技术底座、1 份从"按账期"过渡到"按事件"的 4 阶段路径，以及 3 个反直觉判断。读者是 CFO 和财务经理，看完应该能直接拍板"我们公司要不要做流程再造、怎么做、半年内能拿到什么"。
电商行业涉税面比传统零售宽得多——一家做跨境电商的中型公司，可能同时要面对 6 大税种（增值税、消费税、企业所得税、个人所得税、印花税、关税）的精细化核算，每个税种的计税基础、税率、申报频率、平台代扣场景都不一样。本文把 6 大税种拆成「计税基础 × 平台场景 × 申报节点 × 常见坑」4 个维度逐一拆解，给到一份能直接落到对账系统的税务处理 map——CFO 和税务经理看完，能立刻定位自己公司在哪个税种上还欠着账。
This tutorial centers on DingTalk's topapi/v2/department/listsub open API and consolidates hands-on experience from multiple real integration projects. It systematically covers field semantics, org-tree construction, department mapping with Kingdee Cloud Cosmic, configuration on the Qeasy platform, and common pitfalls, enabling engineers to master the interface in one read.
This guide consolidates the fields, pagination, department filtering, and cross-system mapping practices of the organization user query API, including authentication, request and response structures, extension-field risks, and synchronization governance for CRM user sync, directory maintenance, and permission mapping.
Stripe 的对账难点不在「charge / refund 怎么识别」，而在「**余额（balance）/ 争议（dispute）/ 储备金（reserve）/ 提现（payout）**」4 套账户各自独立运行、按不同时间窗口结算、对账脚本必须按 `created`（业务发生日）入账而非 `available_on`（资金可用日）入账。本文用 7 张图把 5 类余额活动、5 段争议生命周期、5 条 reserve 释放规则、6 条实操 checklist 讲透——给独立站财务一份「4 账户 × 5 活动 × 5 阶段 × 6 checklist」的完整对账地图。
当月底关账的差异表从 5 天压到 2 天，背后真正的工程支点不是「对账引擎」，而是 23 个差异原因结构化标签码。`diffReason` 给机器读、`diffDisposalSuggestion` 给人读，二者采用**不对称落库语义**——机读码每轮重置确保下游集成脚本精准出单，文本建议保留财务人员手补痕迹不被重跑清空。这套「机读 + 人读」双轨是 v3 对账体系里最容易被忽视、但实际承担 80% 自动化收益的工程支点。
This tutorial, grounded in multiple real-world projects, breaks down the "Query Jiandaoyun Material Form Data" API into six parts: scenarios, capabilities, field mapping, Qeasy Cloud configuration, cross-solution best practices, and pitfall retrospectives. Readers can master in one article how this API supports sales-order integration between Jiandaoyun and Kingdee Cloud Cosmic, and how it is encapsulated in the Qeasy Cloud Data Integration Platform.
This tutorial consolidates hands-on experience from multiple customer projects on the Kingdee Cloud Xingchen /jdy/v2/bd/store warehouse query API. It systematically covers field meanings, pagination and incremental mechanisms, the Qeasy platform encapsulation, and real-world pitfalls, helping engineers master the API in one read.
This tutorial focuses on Kingdee Cloud's Purchase Return Application query API, covering field mappings, quantity differences across return/replenish/deduction units, status and bill-type enumerations, and how Qeasy Data Integration platform wraps the interface. It distills common practices and pitfalls from multiple real supply chain integration projects.
This tutorial systematically explains all practical key points of Jky's pagination query interface for return-exchange-replenishment orders in supply chain integration scenarios, covering flattened structure, nested detail expansion, incremental time windows, status code values, field mapping, and pitfall retrospectives, enabling readers to master all key experience of this interface in Jky-to-Kingdee Cloud Skylink integration in one article.
This tutorial systematically covers Kingdee Cloud's executeBillQuery API for the STK_Inventory form, covering request structure, pagination and incremental patterns, key field mappings, and platform encapsulation, distilling cross-scenario practical experience so readers can master all key points of instant inventory integration in one read.
This tutorial consolidates hands-on experience from multiple real-world projects to systematically explain the field mapping, pagination/incremental patterns, pitfall troubleshooting, and configuration on the Qeasy Data Integration Platform for the Jushuitan Qimen Sales Outbound Order API, helping readers master all key integration points in one document.
This tutorial systematically unpacks the Kingdee YXC /jdy/v2/bd/material_brand API in supply chain integration, covering brand master data queries, incremental paging, field mapping, and field-tested lessons learned from multiple SYNC strategies, with guidance on configuring the API on the Qeasy platform.
This tutorial aggregates field-tested experience from multiple customer projects, systematically explaining the order sync interface between Xiaoman OKKI CRM and Digiwin T100, covering field mapping, incremental strategy, code alignment, and exception handling across customer, product, and order documents, with practical configuration guidance on the Qeasy platform.
把过去 18 个月里新用户和开发者最容易复发的 10 个错误拆成 3 大类——数据规范类（4 个，金额符号、双零判定、CONFIRMED 闸、暂估/财务应收并存）、沙箱与脚本类（3 个，不试跑直接保存、OTHER 误用、聚合范式漏注册）、AI Agent 与工程类（3 个，Agent 缺 SKILL、跨店跨平台绑定、v3 重构前残留字段）。每个坑都给出「症状 + 根因 + 防御」三段式，至少 7 个坑附真实数字或版本出处，看完能避开 90% 的重复踩雷。
解析写回后 `incomeAmount = 0` 且 `feeAmount = 0` 的行——也就是账单里的「提现 0 元」「账户内部划转 0 元」「营销两列相抵 0 元」这类行——统一由解析执行层判 `parseStatus = FAILED`，`abnormalReason = "解析后无收入/费用金额"`，不设例外。这条全局规则在 2026-08-06 定稿，覆盖京东 POP / 抖店 / 支付宝 / 亚马逊 / 微信小店 / 速卖通 / 拼多多 / 小红书 / 独立站 9 大平台，是脚本归类结果的「完整性校验」闸——零额 PARSED 残留行会被这条闸直接打成 FAILED，不进任何对账池、不产生"待对账"幽灵记录。实测：亚马逊美站 6 月 42 行双零（订单付款 41 + 订单逆向收费 1）+ 8 行「已推迟」清算（20.22 USD）由 settlement 脚本兜底判 FAILED；支付宝余利宝「转入 / 转出」行的双零行同样命中此规则。
This manual systematically reviews the field structure of the Fenbeitong travel application query API, its script-driven enrichment logic, and the mapping essentials for Kingdee Cloud Cosmos. Distilled from multiple real-world customer projects, it captures proven patterns for primary keys, city sequences, cost-bearing organizations, and accompanying persons, along with configuration paths on the Qeasy Data Integration Platform and a recap of common pitfalls.
年 GMV 18 亿元的电商集团，2024 年 6 月做了一次账务口径切换：从「T+10 月底把账单数据搬到财务系统」改成「订单/退款/库存/物流业务事件出现的那一刻，凭证、毛利、报表同步在落」。切换前后的差距是——财务月结从 11 天压到 3.5 天、退货成本对账从 T+7 提前到 T+1、SKU 级毛利率的 95% 置信区间从「±1.8 个百分点」收紧到「±0.4 个百分点」。本文把这件事拆成 4 个动作。
This tutorial takes the Kingdee Cosmic /jdy/v2/bd/supplier endpoint as the blueprint, aggregating practical experience from multiple retail supply chain integration projects. It systematically covers the supplier query API's capabilities, field mappings, incremental pagination strategies, common pitfalls, and configuration guidance on the Qeasy data integration platform.
