Latest industry insights, tutorials, best practices and case studies.
67 articles
This tutorial systematically consolidates the practical points of querying the Operator master data (BD_OPERATOR) via the Kingdee Cloud executeBillQuery WebAPI. Drawing on multiple real integration projects, it covers field definitions, incremental filters, pagination strategies, and cross-system mapping experience, enabling engineers to master the full integration in one read.
This tutorial centers on P2-342 (Query Kingdee Other Outbound Order, row-by-row), aggregating hands-on experience from multiple supply chain integration projects. It covers executeBillQuery field mappings, request parameters, pagination and incremental patterns, Qeasy platform packaging, and common pitfalls, giving engineers a one-stop reference for cross-system outbound order integration.
抖店的资金账单把所有费用项塞进同一份 CSV——平台服务费、佣金、拦截费、提现、消费者赔付、月付贴息……一个店铺月结就有十几种费用类型，每种还要落到金蝶不同的单据。抖店费用转换脚本 v1.1.0（2026-09-03 用户定稿）用「**流水级直查 + 13 条规则 + 应付带符号净额**」回答这个问题——不经过对账聚合层，直接按「单据类型 × 核算项目」从账单行成单，扣款出正数、退还出红字冲减，单据合计与费用计划聚合净额对平。本文拆开这 13 条规则的分组、应付带符号净额的反直觉之处、v1.1.0 之后的版本演进，以及试跑批次与 Excel 验算锚点。
库存级核算是电商精细化财务核算的"最后一公里"——前 4 个维度（店铺级 / SKU 级 / 毛利级 / 税务级）算的是"账面赚了多少钱"，库存级算的是"账面利润被库存吃掉了多少"。一家年 GMV 5 亿的电商公司，看似 18% 的净利率，扣除「在库滞销 + FBA 长期仓储 + 退货在途 + 缺货损失」4 类隐性库存成本后，真实净利可能只有 6.8%——11.2 个百分点的差额就是库存黑洞。本文给出 CFO 必须看清的 4 类库存成本、多仓核算口径、库存周转"虚假拉长"的 3 大陷阱，以及 FBA 仓 + 国内仓的多仓合并视图。
This tutorial aggregates hands-on experience from real-world private-deployment integration projects, using the Kingdee Cloud Galaxy Sales Order query and the Xiaoshouyi currency and bank account queries as the example. It covers authentication, incremental pagination, nested field extraction, code mapping, scheduling, and retry practices.
最近三个月，业务一线咨询「AI Agent 能不能帮我写脚本」「沙箱安不安全」「能不能撤销」的问题集中在 4 类：能力边界、工作流、安全、知识库。本文按这 4 类递进，挑出最高频的 10 个问题逐条作答——读者可跳到对应编号阅读，也可从头串读。每一问都对应代码里的真实落点，不是 PPT 上的承诺。
亚马逊 Subscribe & Save 订阅服务在 2026 年跨境家居 / 母婴 / 美妆品类的复购率贡献占比 28-42%，但它的财务对账远比普通订单复杂——同一订阅下的不同配送周期（月付 vs 周付）、3 类折扣的叠加（阶梯折扣 + Coupon + Bundle）、跳过订单（Skip）与取消订阅（Cancellation）的两条出口判定，都是境内电商看不到的特殊场景。本文以订阅订单的「分向聚合 × 折扣叠加判定顺序 × 无单守卫 × 跨期归属」为 4 条主线，拆解 Subscribe & Save 对账的工程框架，给出 5 个反直觉结论与 5 步走的实操建议——为订阅订单占 GMV 20%+ 的跨境品牌财务经理提供一份"4 主线 × 5 反直觉 × 5 步走"的操作地图。
This tutorial consolidates hands-on experience from multiple projects around the 'Xiaomi Inventory Query - with stock_age_XM_VIEW' interface, detailing field mapping, stock age aggregation, incremental sync, and pitfall handling, helping engineers complete SQL Server to Xiaomi supply chain inventory integration on the Qeasy platform.
电商行业涉税面比传统零售宽得多——一家做跨境电商的中型公司，可能同时要面对 6 大税种（增值税、消费税、企业所得税、个人所得税、印花税、关税）的精细化核算，每个税种的计税基础、税率、申报频率、平台代扣场景都不一样。本文把 6 大税种拆成「计税基础 × 平台场景 × 申报节点 × 常见坑」4 个维度逐一拆解，给到一份能直接落到对账系统的税务处理 map——CFO 和税务经理看完，能立刻定位自己公司在哪个税种上还欠着账。
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 和财务经理，看完应该能直接拍板"我们公司要不要做流程再造、怎么做、半年内能拿到什么"。
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.
