Latest industry insights, tutorials, best practices and case studies.
455 articles
This tutorial covers the data-cleanup strategy Delete Data Older Than 60 Days within Jushuitan-to-Kingdee Cloud Skylin supply chain integration. It explains the business context, configuration highlights on the Qeasy platform, scheduling details, and common pitfalls, helping enterprise IT teams build a governable historical-data cleanup mechanism.
This guide walks through one concrete purchase-return sync strategy between Jushuitan and Kingdee Cloud, covering field mapping, Qeasy configuration essentials, scheduling, and field-tested pitfalls so engineers can ship faster.
This guide, based on a real supply-chain integration project between Kingdee's cloud accounting platform and an ERP system at a retail enterprise, details a query-only currency synchronization strategy. It explains how to use the Qeasy data integration platform to periodically pull currency records from the source system and land them in the middle layer, with practical lessons on pagination, field mapping, and scheduling.
For read-only master data queries in supply-chain integration, this guide shows how to use Qeasy Data Integration Platform to pull Kingdee Cloud organization info into the middleware layer via executeBillQuery—avoiding dirty writes and acting as a lightweight probe strategy.
电商行业涉税面比传统零售宽得多——一家做跨境电商的中型公司，可能同时要面对 6 大税种（增值税、消费税、企业所得税、个人所得税、印花税、关税）的精细化核算，每个税种的计税基础、税率、申报频率、平台代扣场景都不一样。本文把 6 大税种拆成「计税基础 × 平台场景 × 申报节点 × 常见坑」4 个维度逐一拆解，给到一份能直接落到对账系统的税务处理 map——CFO 和税务经理看完，能立刻定位自己公司在哪个税种上还欠着账。
教育是和服饰、美妆、3C、家居并行的"长履约 + 高退费 + 强中止"对账难题行业——服饰定制 7-15 天、美妆 0-7 天、3C 延保 0-30 天、家居定制 30-120 天,**教育独有的难题是"课时包 90-180 天 + 学期包 120-365 天 + 退课率 18.7% + 学员中止率 7.3% + 课时消耗进度跟踪率 91.4%"** [来源:某在线职业教育品牌 2026 H1 学员行为分析]。**某年 GMV 24.7 亿的中型在线职业教育品牌** 2026 H1 共 **18.7 万笔**订单,课时包占比 **67.4%**、学期包占比 **32.6%**、课时包客单价 **6 720 元**、学期包客单价 **9 487 元**、退课率 **18.7%**、学员中止率 **7.3%**、跨期合同负债 **4.7 亿元**(占总资产 **23.4%**)、学期结业后剩余课时清退占比 **12.4%** [来源:某在线职业教育品牌 2026 H1 订单结构与跨期收入管理报告]。**平台账单只能显示"课时包客单价 6 720 元、学期包 9 487 元"的扣后净额**,
把电商财务的全流程拆开看，过去 18 年的"按账期对账"是"事后算账"——每月 1 次、月底拉账单、手工对账、月初出报表。2026 年的电商日均订单已是 8000-12000 单、退款潮 7-15 天、平台扣点 24 小时波动、月度差异累积 3000 万元是常态。"流程再造"不是把月对改成周对或日对——是把"以账期为单位的批量处理"重新设计为"以业务事件为单位的实时触发"：订单完成、退款完成、佣金结算、平台代扣税、ERP 推送成功 5 类事件各自触发独立流水线。本文给出 5 类业务事件的标准定义、流程再造的 3 层技术底座、1 份从"按账期"过渡到"按事件"的 4 阶段路径，以及 3 个反直觉判断。读者是 CFO 和财务经理，看完应该能直接拍板"我们公司要不要做流程再造、怎么做、半年内能拿到什么"。
2024 年 Temu（拼多多海外）对账逻辑发生「**业务模式两极分化**」的剧变 ——一边是 **Temu 全托管**（商家供货 / 平台代运营代销代发货），一边是 2024 年下半年才大规模放量的 **Temu 半托管**（商家自备货到 Temu 合作海外仓 / 平台负责销售 / 商家自负责售后退货回流 / USD 结算后结汇 CNY）。两种模式对账路径**完全不一样**：全托管走二方核对（无买家订单号），半托管走「**三方两段式**」——平台账单 ↔ 海外仓入库快照 ↔ 商家内部核算 + 资金回流链独立追踪。本文以 2026-08-22 Temu 半托管试点接入定稿记录 + 试点 6 月账期实测为基准，拆透半托管对账新规则 ——核心是 **3 道闸门**（主营收入正循环 SUCCESS / 海外仓入库未映 MISSING_WAREHOUSE / 跨业务类型混淆 ORDER_TYPE_MISMATCH）+ **售后退货回流四件套**（回流单独立记账 + 货品回流登记 + 质检报废标记 + 退运费回拨）+ **USD 结算镜像**（平台收付净额 = 商家 USD 收单合计、商家实收
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.
For B2B retail scenarios, this guide explains how to sync Wangdiantong Other Inbound Orders into Kingdee Xingchen Sales Returns and link them to return request orders. It covers data flow, field mapping, key configuration points in Qeasy, phased implementation steps, and lessons learned.
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.
This guide explains how to use Qeasy Data Integration Platform to recursively pull Feishu employee master data by department into the platform data hub, serving as the lookup source for downstream business documents like purchase orders, sales orders, and expense reimbursements. It covers source parameters, field mapping, the write-null operation pattern, and _findCollection/_mongoQuery cross-strategy queries.
Using channel info sync from a reconciliation system as the entry point, this tutorial shows how to configure a single strategy in the Qeasy Data Integration Platform to land JikeCloud channel master data into a MySQL SRM database on an incremental basis. It covers scenario value, field mapping, configuration essentials, scheduling design, and lessons learned, aimed at integration engineers handling supply-chain master data landing.
This tutorial walks through configuring a 'query-only' strategy on the Qeasy Data Integration Platform to periodically pull provincial auxiliary records from Kingdee Cloud. It covers the business scenario, field mapping, platform configuration essentials, phased scheduling, and common pitfalls.
This guide focuses on a single strategy—other inbound orders—covering the full chain from source query, time-window incremental extraction, to target-side field persistence. The focus areas are time windows, status filtering, header/line staged writes, and centralized code mapping management, giving implementation engineers a directly actionable reference.
For multi-entity supply chain integration, a nutrition and health brand connected its marketing cloud with a cloud ERP using 66 strategies, automating master data (customers, materials), sales outbound, purchase inbound, return inbound, transfers, and inventory writeback. The solution is organized into four phases, covering code mapping, incremental and full sync, token refresh, and health checks, and can be implemented on the Qeasy Data Integration Platform.
For supply-chain integration scenarios, this guide explains how to use Qeasy Data Integration Platform to push error and skipped records from specified strategies in the last 24 hours to an O&M group chat via a WeChat Work bot. It covers data flow, field mapping, configuration essentials, and practical lessons learned.
This article focuses on a specific sync strategy—pushing sales orders from JiKeYun into Yongyou NCC as red-letter sales orders (with logistics company) by agent dimension. It walks through scenarios, data flow, field mapping, configuration on Qeasy, phased scheduling, and lessons learned, written for integration engineers working on supply chain scenarios.
This article uses a manufacturing enterprise's production return order synchronization as a case study, breaking down the complete chain: extracting production return data from a MySQL intermediate database, mapping fields through the Qeasy data integration platform, and writing to Kingdee Cloud. It covers data flow, field mapping, platform configuration, scheduling design, and lessons learned.
一篇文章把 v3 重构后的「双轨认证」讲透：网关层（App-Key + scrypt + 路径级 scope + Redis 限流）防止第三方系统越权调用；应用层（JWT + HMAC-SHA256 + x-gateway-user-id 旁路信任链）防止内部 API 被非法访问；业务层（bcrypt 10 rounds + 5 次错密码锁 15 分钟 + IP 60s/10 次限流）防止密码爆破。三个层级相互独立、又通过「同进程可信通道」串成一条完整的防御链。
