华为MetaERP Oracle Fusion Applications Financials Implementation Guide（Define Customer Account 章节）为锚，向

Oracle Fusion Applications Financials Implementation GuideDefine Customer Account 章节为锚向外补齐完整的 Customer 建模 → 配置步骤 → 与 Fusion 三套架构的关系 → 业务场景核算 → 分录汇总表最后给你一份可直接浏览器打开的 HTMLUI 做了卡片 / 层级树 / 表格 / 代码块中英混排字段名保留英文方便对照 EBS/Fusion。一、先对齐你贴的那段文档到底在讲哪一层那段内容挂在Define Customer Account​ 节点下但它不是从零建 Customer 的全流程而是聚焦在已经有一个 Customer Account 之后在 Account / Site 层要维护哪些子对象Payment DetailsReceipt Methods Payment Instruments→ 决定自动收款用哪家银行、手工收款用哪种方式Communication Information​ → 联系人 / 联系点Account Relationships​ → 母公司账户替子公司付、互开 Bill-to/Ship-toAccount Profiles / Site Profiles​ → 付款条件、逾期策略、Late Charge、DunningProfile Class 版本化是这段最重的逻辑Address Purposes​ → Bill-to / Ship-to / Deliver-to / Bills of Lading / Dunning / Late Charge 六种用途继承搜索顺序Match Receipt By → AutoMatch → AutoCash → AutoInvoice Grouping → Payment Terms → Tax Printing这条是 Fusion AR 的配置级联灵魂也就是说你贴的文档 Customer Account 的属性装配层下面是 TCA 四层建模上面是 Receivables 的交易与核算。二、Fusion 里 Customer 的四层模型TCA这是理解Define Customer Account 与核算/组织/管理架构关系的前提 Party (HZ_PARTIES) └── Customer (selling relationship 标记) └── Customer Account (HZ_CUST_ACCOUNTS) ← 你贴的文档主表 └── Site (Customer Account Site) └── Address Purpose (Bill-to / Ship-to / ...)层级表含义与核算的关系Party​HZ_PARTIES法人/个人/集团身份层不直接参与 AR 核算Customer​Party 标记为 Customer有销售关系的 Party仍不直接挂账Customer Account​HZ_CUST_ACCOUNTS真正进入 AR 的入口信用/付款条件/Profile一个 Party 可挂多个 Account例如集团下商用采购账vs经销商账Site​CUST_ACCT_SITES_ALL地址 PurposeBill-to Site 决定 AutoAccounting 派科目Ship-to 决定税务/交付 关键认知发票/收款/会计科目派生全挂 Customer Account Bill-to Site不挂 Party。所以一个集团下两家子公司分别签单、分别算应收、合并对账这种需求标准做法就是1 Party → 2 Customer Accounts而不是在 Party 层硬扛。三、Define Customer Account 与 Fusion 三套架构的关系Fusion 有三套架构经常被混着说Customer Account 在每一套里的位置不一样1️⃣ 核算架构Ledger / LE / BU / SLAPrimary Ledger └── Legal Entity (LE) └── Business Unit (BU) ← AR 交易发生的单元 └── Transaction Type → 挂 Post to GL Y └── AutoAccounting → 派 Revenue / Receivable / Tax / Freight / Unearned / Unbilled └── 段来源: Bill-to Site / Transaction Type / Salesperson / Standard Lines ...Customer Account 本身不直接挂 Ledger。路径是BU → Transaction Type → AutoAccounting → 借 Bill-to Site 的 COA 段Site 必须通过Reference Data Set (RDS)​ 分配给 BUManage Business Unit Set AssignmentCustomer Account Site 选 RDSSLA Event Class 预定义Invoice / Credit Memo / Debit Memo / Chargeback / Receipt / Misc Receipt / Adjustment / Bills Receivable2️⃣ 组织架构BU / LE / LEDGER SETBU​ AR 业务发生单元谁开的票、谁认收Customer Account可以跨 BU 共享靠 RDS 控制哪些 Site 对哪些 BU 可见LE 层管法人主体出财报的主体Ledger 层管 COA —— Customer Account 不直接感知这两层感知点是 Transaction Type 所在的 BU 再往回追 LE/Ledger3️⃣ 管理架构Profile Class / Collector / Credit / Dunning这就是你贴的文档里Account Profile / Site Profile / Profile Class​ 那一段的归属Profile Class集中定义→ 挂 Payment Terms / Collector / Statement Cycle / Late Charge Policy / DunningAccount Profile继承 Profile Class可覆盖→ 作用于整个 AccountSite Profile继承 Account 或 Profile Class可覆盖→ 作用于单个 Site你文档里那段三档更新策略是关键更新选项行为Apply to new profiles only只影响未来新建的 Account/Site ProfileApply to uncustomized version existing uncustomized应用到未自定义过的 给已有未自定义的开新版本生效日系统日旧版 effective_end昨日Apply to all version all所有用到此 Profile Class 的 Account/Site Profile 全部开新版⚠️ 第三档是暴力全量版本化实施期常用运维期慎用——会批量产生 Profile 历史版本。四、Define Customer Account 详细设置步骤端到端下面这一步序列把你贴的文档嵌到第 6 步以后Phase 1前置核算/组织侧建Primary Ledger LE BUCOA 就位建Receivables System Options现金处理、Commit 频次建Transaction TypesInvoice / CM / DM / CBPost to GLY建Transaction Sources手动 / AutoInvoice / Lockbox建AutoAccounting​ —— 为每个账户类型Revenue / Receivable / Freight / Tax / Unearned / Unbilled / AutoInvoice Clearing …指定段来源Bill-to Site / Transaction Type / Salesperson / Constant建Payment Terms、Statement Cycles、Collectors建Receipt Classes / Receipt Methods自动手工建Remit-to Bank AccountsPhase 2Profile Class管理侧对应你文档的 Profile 段Manage Receivables Customer Profile ClassesProfile Class TabPayment Terms / Collector / Statement Cycle / Currency / Credit LimitLate Charges Tab利率、计算方式、Late Charge Site 指定保存后选三档更新策略之一Phase 3Customer 本体TCA 四层对应你文档的入口Setup → Manage Customers → CreateParty Type Organization / Person填 Account Address必须与Manage Set Assignments for BU里给 Customer Account Site 分配的 RDS 对齐Account 段你文档的 Customer Account 层Account Number可自动关联 Profile ClassPayment Details你文档重点挂Automatic Receipt Methods自动收款用决定 confirm / remit / reconcile 步骤挂Manual Receipt Methods挂Payment Instruments客户银行账户多币种、可绑地址、同币种可多 non-primary、日期可重叠、信用卡Primary 银行账户 自动收款默认扣款户Account Relationships你文档重点One-wayparent 能替 related 付 开 Ship/BillReciprocal双向互付互开勾 Bill-To / Ship-To 才启用地址服务共享系统级Allow payment of unrelated transactions关掉才严格按定义的关系走Communication联系人 / 联系点 / 职责 / 地址可复用 Account Site 地址Sites 段你文档的 Address Purposes 重点至少 1 个Bill-to不开票不行Ship-to → 必须关联一个同 Account 或 related Account 的 Bill-toDeliver-to / Bills of Lading / Dunning / Late Charge 按需每个 Site 可单独建Site Profile继承 Account Profile 或 Profile ClassPhase 4验证跑SLA Create Accounting​ 看 Invoice 能否正确派科目测自动收款客户银行账户 Automatic Receipt Method → 看 funds capture测 Relationshipparent Account 开 Invoice → related Account 付款核销五、业务场景核算逻辑重点Customer Account 怎么驱动分录Fusion AR 的科目不是写在 Customer 上的是AutoAccounting SLA​ 派的但Customer Account / Bill-to Site / Transaction Type​ 是派段的三大源头。下面把常见场景过一遍。场景 1标准开票Standard InvoiceDr Accounts Receivable 10,000 Cr Revenue 10,000 Cr Tax 1,300Receivable 段来源Bill-to Site → 公司段 / 部门段Revenue 段来源Transaction Type 或 SalespersonTax 走 Tax Engine 独立派场景 2贷项通知单Credit Memo全冲Dr Revenue 2,000 Dr Tax 260 Cr Accounts Receivable 2,260→ 标准发票的反向场景 3借项通知单Debit Memo加收运费/罚款Dr Accounts Receivable 1,000 Cr Revenue / Freight 1,000场景 4Rule-based — In Advance先开票分期确认收入例1 月开 3,000、3 个月合同时点分录1 月开票Dr AR 3,000 / CrUnearned Revenue​ 3,0001 月末Dr Unearned 1,000 / Cr Revenue 1,0002 月末Dr Unearned 1,000 / Cr Revenue 1,0003 月末Dr Unearned 1,000 / Cr Revenue 1,000→Unearned Revenue 账户由 AutoAccounting 派段来源通常用 Transaction Type 或 Constant场景 5Rule-based — In Arrears先服务期末开票时点分录1 月末DrUnbilled Receivable​ 1,000 / Cr Revenue 1,0002 月末Dr Unbilled 1,000 / Cr Revenue 1,0003 月末Dr Unbilled 1,000 / Cr Revenue 1,0003 月末同时Dr AR 3,000 / Cr Unbilled 3,000→Unbilled Receivable​ 与 Unearned 别搞反[Unbilled Arrears 先认收后开票][Unearned Advance 先开票后认收]场景 6自动收款核销Receipt → ApplyDr Cash (Remittance Bank) 10,000 Cr Accounts Receivable 10,000若折扣Dr Cash / Dr Discount / Cr AR场景 7LockboxLockbox 处理时 Receipt Match 顺序Site Profile → Account Profile → Lockbox → System Options你文档里的继承链分录同场景 6另可能走Remitted Bills Receivable/Factored Bills Receivable这类 SLA Event Class场景 8Late Charge逾期利息Late Charge Site Profile 或 Bill-to Site Profile 里挂 Late Charge Policy系统选项Statement, Dunning, and Late Charges Site Profiles Used Y→ 用 Late Charge Site 的政策 N → 用 Transaction 所挂 Bill-to Site 的政策你文档原话计息产生 Debit Memo 类分录Dr Accounts Receivable (利息额) Cr Interest Income (利息额)场景 9Adjustment调整Recoverable vs Nonrecoverable Tax你文档关联的 Oracle 例子 Inv 两行 60010% 40020%AR1,140Adj -100RecoverableYDr Revenue 52.63 (10%) 35.09 (20%) Dr Tax 5.26 7.02 Cr AR 100Adj -200RecoverableN税进 Nonrecoverable Tax 不走 Tax RegisterDr Revenue 105.26 70.18 Dr Nonrecoverable Tax 10.52 14.04 Cr AR 200六、业务场景会计核算分录汇总表下面这张是直接给你粘 Excel/实施文档用的口径#业务场景Transaction Type借方贷方科目派生关键来源备注1标准开票InvoiceARRevenue TaxBill-to Site(公司段) TransType(收入段)最基础场景2贷项通知单Credit MemoRevenue TaxAR同源发票反转退货/折让3借项通知单Debit MemoARRevenue / FreightTransType加收/罚款4先开票后确认(In Advance)Invoice Adv RuleAR → Unearned / Unearned → Revenue反向对称Un earned Rev 账户 AutoAccounting3 期示例见场景 45先确认后开票(In Arrears)Invoice Arrears RuleUnbilled → Revenue / AR → Unbilled反向对称Unbilled Rev 账户 AutoAccounting期末一次开票6标准收款核销ReceiptCashARRemittance Bank折扣另走 Discount7Lockbox 收款Receipt(Lockbox)CashARMatch 顺序 Site→Acct→Lockbox→Sys自动匹配8逾期利息 Late ChargeDebit Memo(利息)ARInterest IncomeLate Charge Site Policy依赖 Profile 开关9Adjustment(RecoverableY)AdjustmentRevenue TaxARAdj 的 GL SourceRevenue on InvoiceTax 走 Tax Register10Adjustment(RecoverableN)AdjustmentRevenue Nonrecov TaxAR同上Tax 走 Nonrecov Register11ChargebackChargebackAR(原票) 费用?AR(新 CB) 对方银行?Receipt Class 清账方式退票场景12Write-offAdjustment(Write-off)Bad Debt ExpARReceivables Activity 挂 Bad Debt 账户坏账