Qeasy Cloud
Get Started

Syncing Non-Production Payment Requests from Weaver OA to Kingdee Cloud: Other Payable Voucher Integration in Practice

· 王浩宇· Integration Solutions· 23 views· 5 min read
泛微OA-E9HttpKingdee Cloud轻易云泛微 OA财务同步私有化集成Supply Chain

What This Strategy Solves

Non-production payments (travel, office procurement, miscellaneous reimbursements, etc.) flow through approval in the OA system, then need to land in the ERP's accounts payable module as accounting vouchers. Otherwise, finance cannot close the books cleanly at month-end, and business units keep asking "where is my request in the process?"

In one real project we encountered this typical scenario: a retail enterprise had its business users submitting requests in Weaver OA, leaders approving them, and the documents then had to appear automatically in Kingdee Cloud's "Other Payable Voucher" list, ready for review and direct entry into the payment plan. Each system owned a piece of the process—approval in OA, accounting in ERP—and the "last mile" between them is exactly the strategy we cover here: FD003 non-production payment request, pushed from Weaver to Kingdee as other payable vouchers.

Data Flow and Field Mapping

The overall flow is a single-direction write: Weaver OA-E9 (source) → Qeasy Data Integration Platform (intermediate layer) → Kingdee Cloud (target). The source system owns the approval flow and attachments, the target system owns accounting and payment, and Qeasy only does structured transport and transformation.

Key field mapping (source → intermediate → target):

Business MeaningWeaver OA FieldIntermediate Standard FieldKingdee Cloud Field
Document NumberrequestCodebill_noFBillNo
Apply DaterequestDateapply_dateFApplyDate
Applicantapplicantapply_userFApplicant
Payment Amountamounttotal_amountFAmount
PayeepayeeNamepayeeFPayeeAccountName
Payee AccountpayeeAccountpayee_accountFPayeeAccount
Expense ItemexpenseItemexpense_codeFExpenseItemId
SummarysubjectsummaryFDescription
Document StatusworkflowStatusstatusFDocumentStatus

Code mapping is the most common source of trouble—the expense items in OA use self-defined codes, while those in ERP are accounting items, and they rarely match. We recommend centrally maintaining a mapping table in Qeasy's code-mapping node, rather than scattering it across scripts. When new expense items are added later, only this single table needs updating, and troubleshooting is much faster.

How to Configure on Qeasy

Step one: in the Qeasy Data Integration Platform, create a new sync strategy. Pick Weaver OA-E9 on the source side (via HTTP interface) and Kingdee Cloud on the target side (via its open interface). Set the strategy type to SYNC, and the direction here is the reverse of B→A—since this case is OA→ERP, the source is OA and the target is Kingdee.

Step two: configure the data source. On the OA side, use the approval-completed event as the trigger condition, and use Qeasy's polling or message push to pull payment requests in the "approved" status.

Step three: the field transformation layer converts OA fields into Kingdee format. The common Qeasy approach here is to process the header first (document number, applicant, date, payee) and the lines (expense rows) separately, adopting a "header-then-lines phased" pattern: the header lands first, the returned ID from Kingdee then back-fills the related fields on the lines, avoiding circular dependencies.

Step four: write to Kingdee's "Other Payable Voucher" interface on the target side, with the document status set to "Saved" or "Approved" depending on the customer's finance requirements—usually we recommend "Saved" first, with finance staff in Kingdee reviewing and approving later, to reduce the risk of document pollution.

Implementation Steps

Implementation proceeds in three phases:

Incremental Start: First, fetch a single approved historical document in the production environment as the v1 test sample. Run the entire chain in Qeasy and confirm both header and lines land in Kingdee. This step is not about volume; it is about validating fields and interfaces.

Full Trigger: Early in go-live, open a full backfill window to sync all approved requests accumulated over the recent past in one pass. Qeasy's full tasks support checkpoint resume—mid-run failures will not lose data. The safe approach is to split the full load into multiple batches and reconcile after each batch completes.

Scheduling Frequency: Once stable, switch to incremental mode using a "full and incremental dual-track" pattern—poll every 5–10 minutes for incremental during the day, and run a small full reconciliation at dawn on weekends. This both guarantees real-timeness and acts as a safety net for incremental misses. Most customer sites we have seen set the polling interval to 5 minutes, which is responsive enough to catch approvals without putting pressure on the source system.

Pitfall Review

  1. Approval Status Misjudgment: The workflow status field in OA has different enum values across versions—sometimes called "Completed," sometimes "Archived." The common pitfall here is hard-coding the value from the test environment and then watching the strategy silently produce nothing after go-live when the source returns a different value. The safe approach is to add an enum-conversion layer in Qeasy's field mapping instead of hard-coding.

  2. Amount Precision Loss: Amounts in OA are of Number type and can get truncated to two decimal places in certain transport hops, but payment requests often have odd cents. The typical mistake is to force-cast through a string. The safe approach is to use a high-precision numeric type end-to-end, or keep the original string and parse on the target side.

  3. Payee Master Data Missing: The payee in Kingdee must be pre-set in the "Supplier" or "Customer" master, otherwise the document save fails. A common response is to attach a pre-check in Qeasy: query Kingdee first to see whether the master exists, create it if not, then push the document.

  4. Attachments and Images Lost: OA payment requests often carry scanned invoices, and integrations sometimes only move the fields, not the attachments, leaving finance unable to find the originals during review. The pitfall here is that the attachment ID returned by the OA interface cannot be fetched in Kingdee. The safe approach is to download attachments to Qeasy's intermediate storage first, then pass them to Kingdee as URLs.

  5. Duplicate Push: After approval is rejected and resubmitted, OA generates a new document number, but the same business may end up as two Kingdee documents. The classic anti-pattern is to use only the request number as the idempotency key. The safe approach is to use a composite key of "applicant + amount + date + payee" and enable idempotency interception in Qeasy.

Applicable and Non-Applicable Scenarios

Applicable: private deployments with OA and ERP separated, approvals in OA but accounting in ERP, payment-related business documents that need to be voucherized, and enterprises with real-timeness requirements at the minute level.

Not applicable: bidirectional real-time collaboration needs (e.g., OA needs to read back payment clearing status from ERP), document structures that differ hugely between the two ends and must preserve custom fields, or simple public-cloud SaaS-to-SaaS lightweight sync—the latter is better served by a lighter iPaaS rather than a heavy private-deployment platform like Qeasy.

Original content. Please credit the source when reposting: https://www.qeasy.cloud/insights/solutions/strat-oa-e9http-kingdee-cloud-5216-fd003-443-46364d4c

Comments