> 持续流程改进 > 订单到收款－开票与发票处理 > Salesforce Sales Cloud > 数据模板

您的Order to Cash流程：账单与开票数据模板

Salesforce Sales Cloud

← 返回改进指南

订单到收款－开票与发票处理属性 (19) 订单到收款－开票与发票处理活动 (13) 提取指南 (3)

您的Order to Cash流程：账单与开票数据模板

此模板全面介绍分析Order to Cash流程：账单与开票所需的关键数据属性和活动，列出事件日志需要收集的具体信息，并提供实用的数据提取指导。使用此资源可简化流程挖掘工作，获得有价值的洞察。

建议收集的属性
需要跟踪的关键活动
提取指南

刚接触事件日志？了解如何创建流程挖掘事件日志.

下载模板

订单到收款－开票与发票处理属性

以下是建议纳入事件日志的数据字段，可用于全面分析订单到收款－开票与发票处理流程，确保记录所有关键信息。

3 必需 5 建议 11 可选

	名称	说明
	事件时间 EventTime	表示特定活动发生时间的时间戳。
说明该属性记录每项活动的日期和时间，对于按时间顺序排列事件和分析绩效至关重要。时间戳确定事件顺序，并支持计算事件之间的时长。在流程分析中，Event Time用于计算所有基于时间的指标，包括周期时间、等待时间和特定活动的持续时间。它是“平均发票周期时间”和“DSO”等KPI的基础，也为“发票审批周期时间”和“付款核销绩效”等仪表板提供数据支持。为什么重要该时间戳对于正确排列事件顺序和计算周期时间、持续时间等所有绩效指标至关重要，这些指标是识别延迟的关键。获取位置这些数据通常来自Invoice对象或相关Task/Event记录中的系统生成时间戳字段，例如`CreatedDate`或`LastModifiedDate`。示例 2023-04-15T10:00:00Z2023-04-16T14:30:00Z2023-05-20T09:05:12Z
	发票编号 InvoiceNumber	每张发票的唯一标识符，也是开票流程的主要案例标识。
说明 Invoice Number是将所有相关开票活动归入同一案例的核心属性。每个编号代表发送给客户的一份独立开票单据。在流程挖掘分析中，该属性支持端到端跟踪发票生命周期，从生成到最终付款和关闭。它对于构建流程图，以及计算“平均发票周期时间”和“应收账款周转天数”等案例级KPI至关重要。按Invoice Number分析流程，有助于识别单个开票实例中的瓶颈、返工循环和合规偏差。为什么重要这是关联所有相关开票事件的关键，使您能够完整、端到端地查看每笔独立交易的开票流程。获取位置通常是Salesforce Sales Cloud中Invoice对象的主键，常见形式为`InvoiceNumber`或类似的唯一ID字段。示例 INV-00582INV-01934INV-10345
	活动名称 ActivityName	开票流程中发生的具体业务事件名称。
说明该属性描述发票生命周期中已完成的步骤或达到的里程碑，例如“Invoice Generated”或“Payment Received”。这些活动构成流程图中的节点。分析Activity Name序列是流程挖掘的基础。它能够呈现实际流程，并与设计流程进行对比，用于识别偏差、特定步骤之间的瓶颈和返工循环，直接支持“开票流程返工与错误”和“开票合规违规报告”等仪表板。为什么重要它定义流程步骤，构成流程图的骨架，并支持对工作流、瓶颈和偏差的分析。获取位置通常根据Invoice对象中Status字段的变更，或相关对象（如Task或Event）中记录的具体操作推导得出。示例发票已生成发票已批准发票已发送给客户已收到付款
	付款到期日 PaymentDueDate	客户必须支付发票的日期。
说明该属性指定发票中列明的付款截止日期，根据发票日期和双方约定的付款条款计算得出。 Payment Due Date是财务规划和催收管理的重要数据点，也是衡量实际付款绩效的基准。它对于计算“按时付款率”KPI，以及跟踪付款时效的仪表板（如“应收账款周转天数（DSO）趋势”）至关重要。为什么重要它是衡量付款绩效、计算DSO以及触发付款提醒等催收活动的基准。获取位置这是Salesforce Invoice对象中的标准日期字段，通常命名为`DueDate`。示例 2023-05-152023-06-302023-07-01
	发票总金额 InvoiceTotalAmount	发票的货币总价值。
说明该属性表示客户应为已交付的商品或服务支付的总金额，是每个发票案例的重要财务指标。分析Invoice Total Amount有助于优先处理高价值发票，并了解小额与大额交易在流程绩效上的差异。它可用于仪表板中的分析分组，例如判断高价值发票是否审批时间更长或付款更晚。这对于管理财务风险和有效安排催收工作十分重要。为什么重要它支持财务影响分析，有助于优先处理高价值发票，并了解金额如何影响流程行为，例如审批时间或付款延迟。获取位置这通常是Invoice对象中的标准货币字段，可能命名为`GrandTotal`或类似的汇总字段。示例 5400.5012500.00850.75
	发票状态 InvoiceStatus	发票生命周期中的当前状态。
说明该属性反映发票当前所处状态，例如“Draft”“Awaiting Approval”“Sent”“Paid”或“Void”。它能够随时呈现发票在流程中的位置。 Invoice Status是筛选和分组分析的重要维度。分析人员可以聚焦特定发票群体，例如当前等待付款的全部发票，或所有被拒绝的发票。这有助于确定工作优先级，并分析卡在特定阶段的发票具有哪些特征。为什么重要它清晰呈现发票当前状态，支持对未结、已结或存在问题的案例进行筛选和分析。获取位置这通常是Salesforce发票对象中名为`状态`的标准选项列表字段。示例等待审批已批准已发送给客户已付款已核销
	开票部门 BillingDepartment	负责开票活动的部门或团队。
说明该属性指定责任用户所属的职能团队，例如“应收账款”或“销售运营”。通常根据用户在Salesforce中的个人资料或角色推导得出。按部门分析绩效对于了解流程归属和识别特定团队中的系统性问题至关重要。“付款核销绩效”和“开票团队工作负载与绩效”仪表板使用该属性，对比不同职能领域的效率和资源利用情况。为什么重要它支持团队或部门层面的绩效分析，有助于识别团队特有的瓶颈、资源限制或培训缺口。获取位置这些信息通常存储在Salesforce的用户对象中，字段包括`部门`或`Role.Name`。示例应收账款财务运营催收团队
	责任用户 UserResponsible	执行该活动的用户或代理。
说明该属性标识负责执行特定活动的Salesforce用户，例如批准发票或过账付款的用户。它通常关联到最近修改记录的用户或任务所有者。按责任用户分析流程，有助于了解团队绩效、工作负载分配和培训需求。它通过支持绩效比较和资源分配分析，直接服务于“开票团队工作负载与绩效”仪表板。在调查延迟或错误时，它也有助于开展根因分析。为什么重要它支持个人和团队绩效分析、工作负载平衡，并有助于识别高绩效人员或需要额外培训的用户。获取位置这些信息可在Invoice对象的`LastModifiedById`字段，或相关Task和自定义对象的`OwnerId`字段中找到。还需将这些ID与User对象关联，以获取用户姓名。示例 Alice JohnsonBob WilliamsCharlie Brown
	事件结束时间 EventEndTime	表示活动完成时间的时间戳。
说明该属性记录活动完成时间。开票流程中的许多活动都是瞬时事件，Start Time等于End Time；但审批步骤等活动可能具有可衡量的持续时间。 End Time支持精确计算活动处理时间，即用户或系统实际处理任务的时长。它有助于区分主动工作时间和等待时间，更细致地呈现流程效率。为什么重要它支持精确计算活动处理时间，将主动工作与空闲等待区分开来，从而更准确地分析效率。获取位置这通常不是标准字段，可能需要通过获取案例中后续活动的StartTime推导，或记录在自定义字段中。示例 2023-04-15T10:05:00Z2023-04-16T14:32:10Z2023-05-20T09:05:12Z
	付款条款 PaymentTerms	双方约定的发票付款条件，例如“Net 30”或“Due on Receipt”。
说明该属性定义发票应在何时以及以何种方式支付的规则，通常决定Payment Due Date的计算，也可能包含提前付款折扣条款。按Payment Terms分析有助于了解不同协议如何影响付款行为。这对于“提前付款折扣使用情况”仪表板至关重要，该仪表板通过比较付款日期与付款条款，识别错失的财务机会。它还为部分发票付款周期较长或较短的原因提供背景。为什么重要它为付款截止日期提供背景，是分析付款行为、DSO和提前付款折扣计划有效性的基础。获取位置这些信息可能存储在Salesforce的Invoice对象或关联Account对象的选项列表字段或文本字段中。示例开票后30天付款开票后60天付款10天内付款享受2%折扣，30天内付清收到即付
	最后数据更新时间 LastDataUpdate	源系统最近一次刷新数据的时间戳。
说明该属性表示流程挖掘分析数据最近一次从Salesforce Sales Cloud提取的时间。它是每次刷新时应用于整个数据集的元数据字段。该时间戳有助于用户了解分析数据的新鲜度，确认所查看的仪表板和KPI是否为最新数据。这对于基于流程洞察及时、准确地做出业务决策至关重要。为什么重要告知用户数据的时效性，确保决策基于当前且相关的流程视图。获取位置该值由ETL工具或数据管道在每次执行期间生成并写入数据集。示例 2023-10-27T02:00:00Z2023-10-28T02:00:00Z
	发票币种 InvoiceCurrency	发票金额使用的币种代码，例如USD或EUR。
说明此属性表示发票采用的币种，对于在多个国家/地区运营的组织尤其重要。该字段为财务分析提供必要背景，支持准确汇总货币金额，并比较不同币种区域的流程指标。分析财务KPI时，必须使用此字段进行筛选，以避免混合不同币种。为什么重要为所有货币金额提供必要背景，确保财务分析和报告准确，尤其适用于跨国运营。获取位置通常为标准`CurrencyIsoCode`字段，在启用多币种功能的Salesforce实例中可用。示例 USDEURGBPJPY
	客户名称 CustomerName	被开票客户或账户的名称。
说明该属性标识发票开具对象，即客户或公司。通常通过Salesforce中关联的Account记录获取。按客户分析流程对于了解客户特定行为和识别影响重点客户的问题至关重要。它可以揭示某些客户是否经常延迟付款、需要更多返工，或审批周期较为复杂。这些洞察有助于管理客户关系并制定针对性的催收策略。为什么重要支持以客户为中心的分析，识别经常延迟付款或需要更多发票更正的客户等模式，从而改善客户关系管理。获取位置数据来源于`Account.Name`字段，该字段通过Invoice对象与Account对象之间的查找关系关联。示例 ABC CorporationGlobal Tech Inc.Innovate Solutions LLC
	应收账款周转天数 DaysSalesOutstanding	从发票发送到收到付款所经过的天数。
说明应收账款周转天数（DSO）是一项重要财务指标，用于衡量公司完成销售后平均需要多少天收回款项。其计算时间范围为“Invoice Sent to Customer”事件到“Customer Payment Received”事件。该KPI是Order to Cash流程的重点指标，此属性可为每张发票提供对应数值。它直接支持“Days Sales Outstanding (DSO) Trend”仪表板，对于监控和改善现金流至关重要。为什么重要这是衡量催收流程有效性及其对公司现金流直接影响的关键KPI。获取位置这是一个计算属性，计算方式为`(Timestamp('Customer Payment Received') - Timestamp('Invoice Sent to Customer'))`。示例 32天58天29天
	开票国家 BillingCountry	发票账单地址中指定的国家/地区。
说明此属性记录客户账单地址所在的国家/地区，是对流程数据进行分段分析的重要地理维度。按国家/地区分析账单流程，对于识别绩效、合规和客户行为方面的区域差异至关重要。通过分析可以发现，某些国家/地区是否存在更长的付款周期、更高或不同的返工率，或影响流程的特定监管要求。这有助于推动全球流程标准化和本地化优化。为什么重要支持地理分析，帮助识别绩效、合规要求和付款行为方面的区域差异。获取位置这是Invoice对象标准地址复合字段的一部分，通常为`BillingCountry`。示例 USA德国日本巴西
	是否返工 IsRework	用于标识发票是否经历过返工循环的计算标记。
说明此布尔属性在数据处理过程中生成。当发票的活动序列显示出返工迹象时，该值为true，例如在通过某一阶段后又返回此前阶段（如在“Invoice Approved”之后出现“Invoice Corrected”）。此标记对于快速识别和量化流程低效至关重要。它直接支持“Invoice Rework Rate”KPI和“Billing Process Rework & Errors”仪表板，帮助分析人员筛选并检查成本高、耗时长的返工循环案例。为什么重要通过识别存在纠正循环的案例，直接量化流程低效，帮助定位错误来源并计算质量损失成本。获取位置此属性不在源系统中，而是由流程挖掘工具或ETL层根据每个案例的活动顺序计算得出。示例 truefalse
	是否逾期付款 IsLatePayment	用于标识付款是否在到期日之后收到的计算标记。
说明此布尔属性通过比较“Customer Payment Received”时间戳与“Payment Due Date”生成。付款逾期时为true，否则为false。该标记简化了付款行为和催收效果分析，是“On-Time Payment Rate”KPI的基础，并支持将客户划分为按时付款和逾期付款客户，以便进一步分析。它为每张发票的付款绩效提供清晰的二元结果。为什么重要为催收效果提供清晰的成功指标，直接支持“On-Time Payment Rate”KPI，并支持分析导致付款逾期的因素。获取位置此属性不在源系统中，而是由ETL层或流程挖掘工具通过将付款日期与`PaymentDueDate`字段进行比较计算得出。示例 truefalse
	源系统 SourceSystem	标识数据的来源系统。
说明该属性指定生成事件数据的源应用程序。对于此流程，通常为“Salesforce Sales Cloud”。在多个系统集成的环境中，该字段对于数据血缘和问题排查至关重要。它有助于了解数据背景，确保来自不同系统的事件能够在流程挖掘工具中正确合并和解读。为什么重要它提供有关数据来源的重要背景信息，是多系统环境中开展数据治理、验证和分析的基础。获取位置通常是在数据提取、转换和加载（ETL）过程中添加的静态值，用于标记数据集来源。示例 Salesforce Sales CloudSFSC
	账户负责人 AccountOwner	负责客户账户的销售代表或客户经理。
说明该属性标识客户关系的内部负责人，通常是在Salesforce中分配给Account的销售人员或客户经理。虽然账户负责人不直接参与开票，但可以作为重要分析维度。开票流程中的问题可能影响客户关系，该属性有助于将流程绩效数据与业务拓展侧关联起来。例如，可以分析由特定负责人管理的账户是否更容易出现开票问题。为什么重要将开票流程绩效与客户关系负责人关联起来，有助于了解开票错误或延迟对业务的影响。获取位置这是Account对象中的`Owner.Name`字段，该对象与Invoice相关联。示例 David MillerSophia GarciaJames Wilson

必需建议可选

订单到收款－开票与发票处理活动

以下是建议在事件日志中记录的关键流程步骤和里程碑，可用于准确发现流程并评估绩效。

5 建议 8 可选

	活动	说明
	发票已关闭	发票生命周期已完成，因为款项已全部支付并完成核销。这是发票成功处理的最后一个活动，通常通过状态更新记录。
为什么重要该活动是流程的主要结束点，可用于准确计算端到端周期时间，并为流程分析明确完成标准。获取位置通过Invoice对象状态字段更新为“Closed”“Paid in Full”或类似终态时的时间戳推断。采集发票状态字段变更为最终值“Closed”。事件类型 inferred
	发票已发送给客户	已批准的发票通过电子邮件、邮寄或门户正式送达客户。该事件通常通过填充“Sent Date”字段或将状态变更为“Sent”来捕获。
为什么重要这标志着付款催收周期开始，也是计算应收账款周转天数（DSO）的起点。它是跟踪客户沟通和付款时效的关键里程碑。获取位置通过Invoice对象中“Sent Date”字段被填充，或状态更新为“Sent”来推断。如果通过集成的电子邮件工具发送，也可能作为明确事件记录在Activity History中。采集 “Sent_Date__c”字段被填充时的时间戳。事件类型 inferred
	发票已批准	授权用户已审核并批准发票，确认其准确无误且可以发送给客户。该事件通常在发票状态变更为“Approved”时捕获。
为什么重要这是推动后续开票流程的关键里程碑。此处延迟会造成严重瓶颈，影响DSO和整体周期时间，相关指标由“发票审批周期时间”仪表板衡量。获取位置通过Invoice对象的状态字段变更为“Approved”推断。如果使用Salesforce Approval Processes，也可以从ProcessInstance对象历史记录中明确捕获。采集发票状态字段变更为“Approved”，或正式审批流程步骤完成。事件类型 inferred
	发票已生成	该活动表示在Salesforce中创建新的发票记录。这是特定交易开票流程的正式起点，通常在订单履行完成或达到合同里程碑后触发。该事件的时间取自发票记录的创建时间戳。
为什么重要这是开票流程的主要开始事件。分析从此时到付款的时间，有助于衡量整体订单到现金周期时间，并识别初始数据录入延迟。获取位置该事件取自Salesforce中Invoice自定义对象或代表发票的类似对象的创建日期（CreatedDate字段）。采集发票对象的记录创建时间戳。事件类型 explicit
	已收到客户付款	客户已针对发票付款，资金已经到账。通常通过创建相关“Payment”记录并将其与发票关联来记录。
为什么重要这是现金催收流程中最重要的里程碑，也是计算DSO的终点，表示收入已成功收回。获取位置取自与Invoice对象相关的“Payment”自定义对象记录的创建日期。也可以通过发票状态变更为“Paid”来推断。采集创建相关Payment记录。事件类型 explicit
	付款已过账至总账	收到的付款已正式记录在公司的财务会计系统或总账中。集成运行后，可能通过付款或发票记录的状态更新来捕获。
为什么重要该活动将收款与财务核销区分开来。收款到过账之间的时间可以揭示内部会计流程中的延迟。获取位置通过Payment或Invoice对象的状态字段变更为“Posted”或“Exported to ERP”等值推断，通常由API集成更新。采集付款或发票状态变更为“Posted”。事件类型 inferred
	发票已拒绝	审批人已拒绝发票，通常是因为存在错误或差异，需要修正后重新提交。该事件通过发票记录状态变更为“Rejected”捕获。
为什么重要该活动表示发生返工，流程效率受到影响。分析拒绝频率有助于识别常见错误来源，并为“开票流程返工与错误”仪表板提供根因分析依据。获取位置通过Invoice对象的状态字段变更为“Rejected”推断。相关数据也可能记录在正式Approval Process历史记录的评论中。采集发票状态字段变更为“Rejected”。事件类型 inferred
	发票已提交审批	发票已完成定稿，并在发送给客户前提交内部审核。该活动通常通过发票记录的状态字段变更捕获，例如从“Draft”变为“Pending Approval”。
为什么重要跟踪该活动有助于单独分析审批队列中的耗时，也是计算“平均发票审批时间”KPI的关键步骤。获取位置通过Invoice对象的字段历史记录推断，即状态字段更新为“Submitted for Approval”或“In Review”等值时捕获。采集发票状态字段变更为“Pending Approval”。事件类型 inferred
	发票已更正	表示发票被拒绝或发现错误后进行手动更正或更新。通常可通过发票状态回退到先前状态来推断，例如从“Rejected”回到“Draft”。
为什么重要识别更正循环对于衡量“发票返工率”KPI至关重要。大量更正通常表明初始发票生成流程存在问题，并会导致延迟。获取位置通过字段历史记录跟踪推断，检测状态从后续阶段值（如“Rejected”“Approved”）回退到早期阶段值（如“Draft”“In Progress”）。采集发票状态在流程中回退。事件类型 inferred
	发票已核销	企业已决定取消该债务，发票在未全额付款的情况下关闭。这代表开票流程以失败告终的另一种结果。
为什么重要跟踪核销有助于量化收入损失，并识别导致坏账的客户或情形。这是需要关注的关键异常路径，有助于评估财务健康状况。获取位置通过Invoice对象状态字段更新为“Written Off”或“Canceled - Bad Debt”时的时间戳推断。采集发票状态字段变更为“Written Off”。事件类型 inferred
	已到付款到期日	这是一个计算事件，表示根据发票付款条款应付款的时间点。它不是用户操作，而是根据发票数据推导得出。
为什么重要该活动为分析付款行为和衡量“按时付款率”KPI提供关键基准，有助于区分按时付款和逾期付款。获取位置这是一个计算事件，通过比较当前时间戳与Invoice对象的“Due Date”字段得出。在Salesforce中，它不是存储的事件。采集通过比较当前日期与发票的Due Date字段计算。事件类型 calculated
	已发出付款提醒	已向客户发送通信，提醒其即将到期或已经逾期的付款。该事件通常记录为与发票关联的Activity（Task或Email）记录。
为什么重要跟踪提醒有助于评估催收策略的有效性，也是“付款提醒有效性”仪表板和“付款提醒触发率”KPI的基础。获取位置通过创建与Invoice对象相关的Activity（Task或Email）记录捕获，记录的主题或类型表明其为付款提醒。采集创建具有特定类型或主题的相关Task或Email记录。事件类型 explicit
	现金已应用或核销	收到的付款已在系统中与特定发票完全匹配并完成应用，应收账款随之结清。该事件通过付款或发票记录的最终状态变更捕获。
为什么重要这标志着现金转换周期的最后一步。“付款核销绩效”仪表板依靠该活动衡量财务团队的现金应用效率。获取位置通过Invoice或相关Payment对象的状态变更为“Reconciled”或“Applied”等终态推断。采集发票或付款状态变更为“Reconciled”。事件类型 inferred

建议可选

提取指南

如何从Salesforce Sales Cloud获取数据

步骤

检查前提条件：确保您在Salesforce中拥有必要权限，包括“运行报表”“创建和自定义报表”以及“导出报表”。确认Invoice和Payment对象的关键状态字段已启用Field History Tracking。操作路径为：进入Setup > Object Manager，找到相关对象，进入Fields & Relationships，然后点击“Set History Tracking”。
定义报表策略：由于活动来自不同记录或事件（例如发票创建、状态变化和相关付款），此流程需要创建多个报表。请为每个不同来源分别创建报表，然后在外部合并结果。
创建记录创建报表：从最简单的活动开始。为“发票已生成”和“已收到客户付款”创建报表。进入Reports选项卡并点击“New Report”。选择包含Invoice对象（例如“Invoices”）或Payment对象的报表类型。添加与事件日志属性对应的列。对于“发票已生成”活动，发票记录的CreatedDate将作为EventTime。
创建字段历史报表：要捕获“发票已提交审批”“发票已批准”“发票已拒绝”和“发票已更正”等状态变化，请基于“Invoice History”报表类型创建报表。该特殊报表类型会显示Field History Tracking记录的变化。请筛选状态字段的变化。
创建基于日期的活动报表：对于“已向客户发送发票”或“已到付款到期日”等活动，请在Invoice对象上创建报表。使用日期字段本身（如Sent_Date__c或Payment_Due_Date__c）作为EventTime，并筛选这些日期不为空的记录。
创建相关活动报表：对于“已发出付款提醒”等活动，需要创建将Activities（Task或Event）与Invoices关联的报表。使用“Activities with Invoices”等报表类型，或创建自定义报表类型。筛选主题或类型明确表示提醒的活动。
为所有报表添加标准列：在创建每个报表时，确保添加可映射到所需事件日志结构的列：InvoiceNumber、EventTime字段（如CreatedDate或字段变更日期）、UserResponsible（如LastModifiedById）以及其他建议属性。
将报表导出为CSV：分别运行每个报表。在报表结果页面中使用下拉菜单选择“Export”，并选择带有.csv扩展名的“Details Only”格式。对创建的所有报表重复此操作。
合并并转换数据：在电子表格程序中打开导出的CSV文件，或使用数据准备工具。为每个文件新增名为ActivityName的列，并填入其代表的具体活动（例如，为第一份报表的所有行填入“发票已生成”）。将源列（例如Invoice: Created Date）映射到标准事件日志标题（EventTime）。
创建最终事件日志：将各个CSV文件中的转换后数据整合到一个主文件中。确保列标题准确为InvoiceNumber、ActivityName、EventTime、UserResponsible等。该统一文件就是最终事件日志。
最终格式化：使用UTF-8编码将整合后的文件保存为CSV。现在，该文件已可上传到ProcessMind。

配置

报表类型：您可能需要多个自定义报表类型，将Account等父对象与Invoice、Payment和Activity等子对象及孙对象连接起来。请在Setup > Report Types中创建这些报表类型。
字段历史跟踪：这一步至关重要。请为Invoice对象的任何状态字段启用历史跟踪。否则，无法捕获“已批准”或“已拒绝”等状态变化活动。历史记录不会追溯记录。
数据筛选器：始终为报表应用日期筛选器，以控制数据量。建议将主对象的创建日期筛选为最近3到6个月（例如，Invoice: Created Date等于LAST 180 DAYS）。
数据导出服务：您也可以使用原生Data Export Service（Setup > Data Export），替代分别运行各个报表。该服务每周或每月导出组织的全部数据，可提供完整备份，但需要大量后处理，才能将数据筛选、关联并转换为事件日志。
用户权限：执行提取的用户需要拥有所有相关对象（例如Account、Order、Invoice__c、Payment__c和Activity）及字段的读取权限，同时还需要创建和导出报表的权限。

a 示例查询 config

// This is a configuration guide for building multiple Salesforce reports.
// The data from these separate CSV exports must be manually combined and transformed into a single event log.

// Report 1: Invoice Generated
// Report Type: Invoices (or your custom invoice object report type)
// Filters: 
// 1. Created Date GREATER OR EQUAL [Start Date]
// 2. Created Date LESS OR EQUAL [End Date]
// Columns to Export & Map:
// - Invoice Number -> InvoiceNumber
// - 'Invoice Generated' (static text) -> ActivityName
// - Created Date -> EventTime
// - Created By -> UserResponsible
// - [Billing Department Field] -> BillingDepartment
// - Status -> InvoiceStatus
// - Total Amount -> InvoiceTotalAmount
// - Payment Due Date -> PaymentDueDate

// Report 2: Invoice Status Changes (Submitted, Approved, Rejected, Corrected, Closed, Written Off)
// Report Type: Invoice History (or your custom object's history report type)
// Filters:
// 1. Edit Date GREATER OR EQUAL [Start Date]
// 2. Edit Date LESS OR EQUAL [End Date]
// 3. Field/Event EQUALS 'Status' (or the name of your status field)
// Columns to Export & Map:
// - Invoice Number -> InvoiceNumber
// - New Value (transformed*) -> ActivityName 
// - Edit Date -> EventTime
// - Edited By -> UserResponsible
// - [Billing Department Field] -> BillingDepartment
// - New Value -> InvoiceStatus
// - [Invoice Total Amount] -> InvoiceTotalAmount
// - [Invoice Payment Due Date] -> PaymentDueDate
// *Transformation Logic for ActivityName: 
//   - IF New Value = 'Pending Approval' THEN 'Invoice Submitted for Approval'
//   - IF New Value = 'Approved' THEN 'Invoice Approved'
//   - IF New Value = 'Rejected' THEN 'Invoice Rejected'
//   - IF New Value = 'Draft' AND Old Value = 'Rejected' THEN 'Invoice Corrected'
//   - IF New Value = 'Closed' THEN 'Invoice Closed'
//   - IF New Value = 'Written Off' THEN 'Invoice Written Off'

// Report 3: Invoice Sent to Customer
// Report Type: Invoices
// Filters:
// 1. [Sent Date Field] NOT EQUAL TO "" (not null)
// 2. [Sent Date Field] GREATER OR EQUAL [Start Date]
// 3. [Sent Date Field] LESS OR EQUAL [End Date]
// Columns to Export & Map:
// - Invoice Number -> InvoiceNumber
// - 'Invoice Sent to Customer' (static text) -> ActivityName
// - [Sent Date Field] -> EventTime
// - Last Modified By -> UserResponsible
// - [Billing Department Field] -> BillingDepartment
// - Status -> InvoiceStatus
// - Total Amount -> InvoiceTotalAmount
// - Payment Due Date -> PaymentDueDate

// Report 4: Payment Due Date Reached
// Report Type: Invoices
// Filters:
// 1. Payment Due Date NOT EQUAL TO "" (not null)
// 2. Payment Due Date GREATER OR EQUAL [Start Date]
// 3. Payment Due Date LESS OR EQUAL [End Date]
// Columns to Export & Map:
// - Invoice Number -> InvoiceNumber
// - 'Payment Due Date Reached' (static text) -> ActivityName
// - Payment Due Date -> EventTime
// - 'System' (static text) -> UserResponsible
// - [Billing Department Field] -> BillingDepartment
// - Status -> InvoiceStatus
// - Total Amount -> InvoiceTotalAmount
// - Payment Due Date -> PaymentDueDate

// Report 5: Payment Reminder Issued
// Report Type: Activities with Invoices (or similar custom report type)
// Filters:
// 1. Task or Event Subject CONTAINS 'Payment Reminder'
// 2. Created Date GREATER OR EQUAL [Start Date]
// 3. Created Date LESS OR EQUAL [End Date]
// Columns to Export & Map:
// - Invoice: Invoice Number -> InvoiceNumber
// - 'Payment Reminder Issued' (static text) -> ActivityName
// - Created Date -> EventTime
// - Assigned To -> UserResponsible
// - [Billing Department Field] -> BillingDepartment
// - [Invoice Status Field] -> InvoiceStatus
// - [Invoice Total Amount] -> InvoiceTotalAmount
// - [Invoice Payment Due Date] -> PaymentDueDate

// Report 6: Customer Payment Received & Status Changes (Posted, Applied)
// Report Type: Payments with Invoices (or similar custom report type)
// This report combines multiple events from the Payment record.
// Filters:
// 1. Payment: Created Date GREATER OR EQUAL [Start Date]
// 2. Payment: Created Date LESS OR EQUAL [End Date]
// Part A: Payment Received
// Columns to Export & Map:
// - Invoice: Invoice Number -> InvoiceNumber
// - 'Customer Payment Received' (static text) -> ActivityName
// - Payment: Created Date -> EventTime
// - Payment: Created By -> UserResponsible
// Part B: Payment Posted and Applied (Requires exporting and transforming multiple rows for the same payment if status changes)
// You may need a separate Payment History Report, similar to Report 2.
// Assuming a simple status field on the Payment for this example:
//   - IF Payment Status = 'Posted' THEN 'Payment Posted to Ledger'
//   - IF Payment Status = 'Applied' THEN 'Cash Applied/Reconciled'

步骤

前提条件和设置：确保系统已安装Python 3.6或更高版本。在终端运行以下命令安装所需库：pip install simple-salesforce pandas。您还需要Salesforce用户名、密码和安全令牌。获取安全令牌的方法：登录Salesforce，进入个人设置，找到“Reset My Security Token”选项。
启用Field History Tracking：以管理员身份登录Salesforce组织。进入Setup，然后进入Object Manager。找到主要Invoice对象，例如Invoice__c，进入“Fields & Relationships”，点击“Set History Tracking”。为代表发票状态的字段启用跟踪，例如Status__c。对Payment对象及其对应状态字段重复此操作，例如Payment__c。
下载并配置脚本：将提供的Python脚本保存为extract_invoices.py。使用文本编辑器打开文件，更新“Salesforce Credentials and Settings”部分的占位值。您必须填写SF_USERNAME、SF_PASSWORD、SF_SECURITY_TOKEN和SF_INSTANCE_URL。调整START_DATE和END_DATE以定义提取时间范围。
自定义对象和字段名称：仔细检查脚本中的SOQL查询。脚本使用Invoice__c、Payment__c、Status__c、Total_Amount__c等占位名称。您必须将其替换为Salesforce实例中账单和开票所用对象及字段的实际API名称。
执行提取脚本：打开终端或命令提示符，进入脚本保存目录，并运行命令：python extract_invoices.py。脚本将连接Salesforce API、执行查询并处理数据。
监控脚本进度：脚本获取并处理各类活动数据时，会在控制台输出状态消息。根据数据量和API限制，处理可能需要一段时间。请留意可能表示凭据或API名称错误的报错信息。
检查输出文件：脚本成功完成后，会在同一目录生成salesforce_billing_event_log.csv文件。请使用电子表格程序打开该CSV文件，检查内容并确认数据符合预期。
准备上传：生成的CSV文件包含所需列InvoiceNumber、ActivityName和EventTime，以及其他推荐属性。无需进一步格式处理，即可直接将文件上传到流程挖掘工具。

配置

Salesforce凭据：您必须提供Salesforce用户名、密码和安全令牌。从组织可信IP范围之外访问API时，需要使用安全令牌。
Salesforce实例URL：请指定Salesforce实例的域名，例如your_instance.my.salesforce.com。如果使用沙盒环境，URL会有所不同，例如test.salesforce.com。
日期范围筛选：脚本包含START_DATE和END_DATE变量。建议先使用3至6个月等较短日期范围，以控制数据量并遵守API限制。这些日期用于筛选初始查询中的发票创建日期。
对象和字段API名称：脚本使用对象和字段的占位API名称，例如Invoice__c和Status__c。您必须将其替换为Salesforce数据模型中的准确API名称。可在Salesforce Setup的Object Manager中查看。
跟踪前提条件：事件日志的准确性，尤其是状态变更的准确性，完全取决于相关字段是否在交易发生前已启用Salesforce Field History Tracking。如果未启用，则不会记录历史变更。
API调用限制：Salesforce对24小时内可执行的API调用次数实施治理限制。对于超大数据集，请考虑分成较小的日期范围批次提取，或安排在业务低峰期运行，以避免触发限制。

a 示例查询 python

import pandas as pd
from simple_salesforce import Salesforce
from datetime import datetime

class=class="hl-string">"hl-comment"># --- Salesforce Credentials and Settings ---
class=class="hl-string">"hl-comment"># IMPORTANT: Replace all placeholder values with your actual Salesforce information.
SF_USERNAME = class="hl-string">'[your_salesforce_username]'
SF_PASSWORD = class="hl-string">'[your_salesforce_password]'
SF_SECURITY_TOKEN = class="hl-string">'[your_salesforce_security_token]' class=class="hl-string">"hl-comment"># Append this to your password if required
SF_INSTANCE_URL = class="hl-string">'https://[your_instance].my.salesforce.com' class=class="hl-string">"hl-comment"># e.g., na1.salesforce.com

class=class="hl-string">"hl-comment"># --- Extraction Period ---
START_DATE = class="hl-string">'2023-01-01T00:00:00Z'
END_DATE = class="hl-string">'2023-12-31T23:59:59Z'

class=class="hl-string">"hl-comment"># --- Object and Field API Name Placeholders ---
class=class="hl-string">"hl-comment"># Replace these with the actual API names from your Salesforce org.
INVOICE_OBJECT = class="hl-string">'Invoice__c'
INVOICE_NUMBER_FIELD = class="hl-string">'Name'
INVOICE_STATUS_FIELD = class="hl-string">'Status__c'
INVOICE_TOTAL_AMOUNT_FIELD = class="hl-string">'Total_Amount__c'
INVOICE_DUE_DATE_FIELD = class="hl-string">'Due_Date__c'

PAYMENT_OBJECT = class="hl-string">'Payment__c'
PAYMENT_INVOICE_LOOKUP_FIELD = class="hl-string">'Invoice__c' class=class="hl-string">"hl-comment"># Lookup field from Payment to Invoice
PAYMENT_STATUS_FIELD = class="hl-string">'Status__c'

class=class="hl-string">"hl-comment"># --- Main Script ---
def main():
    print(class="hl-string">"Connecting to Salesforce...")
    sf = Salesforce(username=SF_USERNAME, password=SF_PASSWORD, security_token=SF_SECURITY_TOKEN, instance_url=SF_INSTANCE_URL)
    print(class="hl-string">"Connection successful.")

    all_events = []

    class=class="hl-string">"hl-comment"># 1. Get base Invoice data
    print(class="hl-string">"Fetching base invoice data...")
    soql_invoices = fclass="hl-string">"""
        SELECT Id, {INVOICE_NUMBER_FIELD}, CreatedDate, CreatedById, LastModifiedById, 
               {INVOICE_STATUS_FIELD}, {INVOICE_TOTAL_AMOUNT_FIELD}, {INVOICE_DUE_DATE_FIELD}
        FROM {INVOICE_OBJECT}
        WHERE CreatedDate >= {START_DATE} AND CreatedDate <= {END_DATE}
    """
    invoices_data = sf.query_all(soql_invoices)[class="hl-string">'records']
    df_invoices = pd.DataFrame(invoices_data).drop(columns=[class="hl-string">'attributes'])
    invoice_ids = class="hl-string">"','".join(df_invoices[class="hl-string">'Id'].tolist())

    class=class="hl-string">"hl-comment"># Activity: Invoice Generated & Payment Due Date Reached
    print(class="hl-string">"Processing 'Invoice Generated' and 'Payment Due Date Reached' events...")
    generated_events = df_invoices.copy()
    generated_events[class="hl-string">'ActivityName'] = class="hl-string">'Invoice Generated'
    generated_events[class="hl-string">'EventTime'] = pd.to_datetime(generated_events[class="hl-string">'CreatedDate']).dt.tz_localize(None)
    generated_events[class="hl-string">'UserResponsible'] = generated_events[class="hl-string">'CreatedById']
    all_events.append(generated_events)

    due_date_events = df_invoices[df_invoices[INVOICE_DUE_DATE_FIELD].notna()].copy()
    due_date_events[class="hl-string">'ActivityName'] = class="hl-string">'Payment Due Date Reached'
    due_date_events[class="hl-string">'EventTime'] = pd.to_datetime(due_date_events[INVOICE_DUE_DATE_FIELD]).dt.tz_localize(None)
    due_date_events[class="hl-string">'UserResponsible'] = None class=class="hl-string">"hl-comment"># System-generated event
    all_events.append(due_date_events)

    class=class="hl-string">"hl-comment"># 2. Get Invoice Status Changes from Field History
    print(class="hl-string">"Fetching invoice status changes...")
    soql_invoice_history = fclass="hl-string">"""
        SELECT ParentId, Field, OldValue, NewValue, CreatedDate, CreatedById
        FROM {INVOICE_OBJECT}History
        WHERE ParentId IN ('{invoice_ids}') AND Field = '{INVOICE_STATUS_FIELD}'
    """
    invoice_history_data = sf.query_all(soql_invoice_history)[class="hl-string">'records']
    if invoice_history_data:
        df_invoice_history = pd.DataFrame(invoice_history_data).drop(columns=[class="hl-string">'attributes'])
        df_invoice_history = df_invoice_history.merge(df_invoices[[class="hl-string">'Id', INVOICE_NUMBER_FIELD, INVOICE_TOTAL_AMOUNT_FIELD, INVOICE_DUE_DATE_FIELD]], left_on=class="hl-string">'ParentId', right_on=class="hl-string">'Id')
        df_invoice_history[class="hl-string">'EventTime'] = pd.to_datetime(df_invoice_history[class="hl-string">'CreatedDate']).dt.tz_localize(None)
        df_invoice_history[class="hl-string">'UserResponsible'] = df_invoice_history[class="hl-string">'CreatedById']

        class=class="hl-string">"hl-comment"># Map status changes to Activity Names
        status_map = {
            (class="hl-string">'Draft', class="hl-string">'Pending Approval'): class="hl-string">'Invoice Submitted for Approval',
            (class="hl-string">'Pending Approval', class="hl-string">'Approved'): class="hl-string">'Invoice Approved',
            (class="hl-string">'Pending Approval', class="hl-string">'Rejected'): class="hl-string">'Invoice Rejected',
            (class="hl-string">'Rejected', class="hl-string">'Draft'): class="hl-string">'Invoice Corrected',
            (class="hl-string">'Approved', class="hl-string">'Sent'): class="hl-string">'Invoice Sent to Customer',
            (class="hl-string">'Approved', class="hl-string">'Closed'): class="hl-string">'Invoice Closed',
            (class="hl-string">'Sent', class="hl-string">'Closed'): class="hl-string">'Invoice Closed',
            (class="hl-string">'Approved', class="hl-string">'Written Off'): class="hl-string">'Invoice Written Off'
        }
        df_invoice_history[class="hl-string">'ActivityName'] = df_invoice_history.apply(lambda row: status_map.get((str(row[class="hl-string">'OldValue']), str(row[class="hl-string">'NewValue']))), axis=1)
        df_invoice_history.rename(columns={class="hl-string">'NewValue': INVOICE_STATUS_FIELD}, inplace=True)
        all_events.append(df_invoice_history.dropna(subset=[class="hl-string">'ActivityName']))

    class=class="hl-string">"hl-comment"># 3. Get Payment Reminders from Tasks
    print(class="hl-string">"Fetching payment reminder tasks...")
    soql_tasks = fclass="hl-string">"""
        SELECT WhatId, ActivityDate, CreatedById, CreatedDate
        FROM Task
        WHERE WhatId IN ('{invoice_ids}') AND Subject LIKE '%Payment Reminder%'
    """
    task_data = sf.query_all(soql_tasks)[class="hl-string">'records']
    if task_data:
        df_tasks = pd.DataFrame(task_data).drop(columns=[class="hl-string">'attributes'])
        df_tasks = df_tasks.merge(df_invoices[[class="hl-string">'Id', INVOICE_NUMBER_FIELD, INVOICE_STATUS_FIELD, INVOICE_TOTAL_AMOUNT_FIELD, INVOICE_DUE_DATE_FIELD]], left_on=class="hl-string">'WhatId', right_on=class="hl-string">'Id')
        df_tasks[class="hl-string">'ActivityName'] = class="hl-string">'Payment Reminder Issued'
        df_tasks[class="hl-string">'EventTime'] = pd.to_datetime(df_tasks[class="hl-string">'CreatedDate']).dt.tz_localize(None)
        df_tasks[class="hl-string">'UserResponsible'] = df_tasks[class="hl-string">'CreatedById']
        all_events.append(df_tasks)

    class=class="hl-string">"hl-comment"># 4. Get Payment Data
    print(class="hl-string">"Fetching payment data...")
    soql_payments = fclass="hl-string">"""
        SELECT Id, {PAYMENT_INVOICE_LOOKUP_FIELD}, CreatedDate, CreatedById, LastModifiedById, {PAYMENT_STATUS_FIELD}
        FROM {PAYMENT_OBJECT}
        WHERE {PAYMENT_INVOICE_LOOKUP_FIELD} IN ('{invoice_ids}')
    """
    payment_data = sf.query_all(soql_payments)[class="hl-string">'records']
    if payment_data:
        df_payments = pd.DataFrame(payment_data).drop(columns=[class="hl-string">'attributes'])
        df_payments = df_payments.merge(df_invoices[[class="hl-string">'Id', INVOICE_NUMBER_FIELD, INVOICE_TOTAL_AMOUNT_FIELD, INVOICE_DUE_DATE_FIELD]], left_on=PAYMENT_INVOICE_LOOKUP_FIELD, right_on=class="hl-string">'Id', suffixes=(class="hl-string">'_payment', class="hl-string">'_invoice'))
        payment_ids = class="hl-string">"','".join(df_payments[class="hl-string">'Id_payment'].tolist())
        
        class=class="hl-string">"hl-comment"># Activity: Customer Payment Received
        payment_received_events = df_payments.copy()
        payment_received_events[class="hl-string">'ActivityName'] = class="hl-string">'Customer Payment Received'
        payment_received_events[class="hl-string">'EventTime'] = pd.to_datetime(payment_received_events[class="hl-string">'CreatedDate']).dt.tz_localize(None)
        payment_received_events[class="hl-string">'UserResponsible'] = payment_received_events[class="hl-string">'CreatedById']
        all_events.append(payment_received_events)
        
        class=class="hl-string">"hl-comment"># 5. Get Payment Status Changes
        print(class="hl-string">"Fetching payment status changes...")
        soql_payment_history = fclass="hl-string">"""
            SELECT ParentId, Field, OldValue, NewValue, CreatedDate, CreatedById
            FROM {PAYMENT_OBJECT}History
            WHERE ParentId IN ('{payment_ids}') AND Field = '{PAYMENT_STATUS_FIELD}'
        """
        payment_history_data = sf.query_all(soql_payment_history)[class="hl-string">'records']
        if payment_history_data:
            df_payment_history = pd.DataFrame(payment_history_data).drop(columns=[class="hl-string">'attributes'])
            df_payment_history = df_payment_history.merge(df_payments[[class="hl-string">'Id_payment', INVOICE_NUMBER_FIELD, INVOICE_TOTAL_AMOUNT_FIELD, INVOICE_DUE_DATE_FIELD]], left_on=class="hl-string">'ParentId', right_on=class="hl-string">'Id_payment')
            df_payment_history[class="hl-string">'EventTime'] = pd.to_datetime(df_payment_history[class="hl-string">'CreatedDate']).dt.tz_localize(None)
            df_payment_history[class="hl-string">'UserResponsible'] = df_payment_history[class="hl-string">'CreatedById']

            payment_status_map = {
                (class="hl-string">'Received', class="hl-string">'Posted'): class="hl-string">'Payment Posted to Ledger',
                (class="hl-string">'Posted', class="hl-string">'Reconciled'): class="hl-string">'Cash Applied/Reconciled'
            }
            df_payment_history[class="hl-string">'ActivityName'] = df_payment_history.apply(lambda row: payment_status_map.get((str(row[class="hl-string">'OldValue']), str(row[class="hl-string">'NewValue']))), axis=1)
            df_payment_history.rename(columns={class="hl-string">'NewValue': INVOICE_STATUS_FIELD}, inplace=True)
            all_events.append(df_payment_history.dropna(subset=[class="hl-string">'ActivityName']))

    class=class="hl-string">"hl-comment"># --- Final Assembly ---
    print(class="hl-string">"Assembling final event log...")
    final_df = pd.concat(all_events, ignore_index=True)

    class=class="hl-string">"hl-comment"># Standardize column names
    final_df.rename(columns={
        INVOICE_NUMBER_FIELD: class="hl-string">'InvoiceNumber',
        INVOICE_STATUS_FIELD: class="hl-string">'InvoiceStatus',
        INVOICE_TOTAL_AMOUNT_FIELD: class="hl-string">'InvoiceTotalAmount',
        INVOICE_DUE_DATE_FIELD: class="hl-string">'PaymentDueDate'
    }, inplace=True)

    class=class="hl-string">"hl-comment"># Select and order columns for the final event log
    required_cols = {
        class="hl-string">'InvoiceNumber': None,
        class="hl-string">'ActivityName': None,
        class="hl-string">'EventTime': None,
        class="hl-string">'UserResponsible': None,
        class="hl-string">'InvoiceStatus': None,
        class="hl-string">'InvoiceTotalAmount': None,
        class="hl-string">'PaymentDueDate': None
    }
    for col in required_cols:
        if col not in final_df.columns:
            final_df[col] = required_cols[col]
    
    class=class="hl-string">"hl-comment"># We cannot extract Billing Department directly from this model, so we will add it as an empty column
    final_df[class="hl-string">'BillingDepartment'] = None

    final_df = final_df[list(required_cols.keys()) + [class="hl-string">'BillingDepartment']]

    class=class="hl-string">"hl-comment"># Sort by case and event time
    final_df.sort_values(by=[class="hl-string">'InvoiceNumber', class="hl-string">'EventTime'], inplace=True)

    class=class="hl-string">"hl-comment"># Save to CSV
    output_filename = class="hl-string">'salesforce_billing_event_log.csv'
    final_df.to_csv(output_filename, index=False, date_format=class="hl-string">'%Y-%m-%dT%H:%M:%S.%f')
    print(fclass="hl-string">"Event log saved to {output_filename}")

if __name__ == class="hl-string">'__main__':
    main()

步骤

选择支持Salesforce Sales Cloud连接器的ETL或iPaaS平台，并使用所需的Salesforce身份验证方式创建连接。仅在平台配置中填写连接字符串、凭据、组织标识符或环境专属值。
确认已连接的Salesforce组织提供发票对象、发票状态历史或审计来源、相关活动记录、付款记录，以及流程所需的会计集成记录。将查询中的每个方括号对象或字段引用替换为Salesforce环境中配置的对应名称。
配置增量提取的开始日期和结束日期参数。根据实际情况使用发票创建日期、状态变更日期、活动日期、付款日期、过账日期、对账日期和关闭日期。请提取足够的回溯时间范围，以纳入在所选期间之前创建但在该期间仍处于活动状态的案例。
将下方完整查询添加到ETL工具的Salesforce查询或转换组件中。如果连接器不支持所示查询语法，请使用可视化源、筛选、连接、计算字段和联合组件复现相同逻辑。不要依赖ProcessMind从状态变更推断事件，因为每项活动都必须作为明确的事件日志行输出。
配置发票对象、发票状态历史或审计来源、相关活动记录、付款记录、分类账过账记录和对账记录的源映射。将发票编号映射到InvoiceNumber，将活动标签映射到ActivityName，将相关时间戳映射到EventTime。源数据可用时，请保留推荐属性。
应用转换规则。将所有时间戳转换为统一时区，规范化状态值，将InvoiceTotalAmount转换为数值类型，将PaymentDueDate转换为日期或时间戳类型，并删除缺少InvoiceNumber或EventTime的记录。对于Payment Due Date Reached，仅当到期日位于提取窗口内且发票记录可用时，才使用PaymentDueDate作为EventTime输出明确事件行。
使用InvoiceNumber、ActivityName、EventTime以及可用的源记录标识符对事件去重。如果源数据包含多次合法提交、拒绝、提醒、纠正、付款、过账或对账事件，请保留这些独立发生记录。
验证输出是否包含全部13个必需的ActivityName值，且每行都有InvoiceNumber和EventTime。在源数据支持的情况下，确认每张发票内的事件时间戳顺序正确。
将转换结果加载为CSV、Parquet或ProcessMind支持的其他事件日志格式。使用InvoiceNumber作为案例标识符，ActivityName作为活动列，EventTime作为事件时间列。将UserResponsible、BillingDepartment、InvoiceStatus、InvoiceTotalAmount和PaymentDueDate作为附加属性。
导出最终事件日志并上传到ProcessMind。导入时确认ProcessMind按原样读取这些行，无需推导任何缺失活动。

配置

连接器：使用ETL或iPaaS平台预置的Salesforce连接器，并使用具有所有已配置发票、状态历史、活动、付款、分类账和对账数据源读取权限的集成用户完成身份验证。
对象和字段映射：将[Invoice object]、[Invoice Number field]、[Invoice Created Date field]及其他所有方括号引用替换为目标Salesforce组织中的实际名称。Salesforce通常使用自定义对象和字段，因此必须验证映射，不能凭假设配置。
日期范围：先使用3至6个月的数据。当发票可能跨报告期间保持未结状态时，延长回溯周期，并为状态变更、付款、提醒和对账事件设置边界缓冲期。
增量提取：在可用时，根据最近一次成功提取的源修改时间戳设置水位线。将水位线存储在事件日志之外，并重新处理一个较小的重叠时间窗口，避免遗漏延迟到达的更新。
筛选条件：仅在分析明确要求时，应用公司、业务部门、法人实体、货币、发票类型和生命周期筛选条件。将[Company filter]和[Document type filter]替换为组织特定的条件；如不适用，则移除这些条件。
状态历史：优先选择能够保留每次状态转换的数据源。仅依靠当前发票状态字段，无法可靠重建此前的审批、拒绝、更正、发送、关闭或核销事件。
计算到期日事件：Payment Due Date Reached由PaymentDueDate生成，并非Salesforce用户操作。请明确该事件应针对所有发票生成，还是仅针对在到期日仍处于未结状态的发票生成。
关联记录：使用Salesforce组织中的实际关联键配置连接。不要假设不同实现中的发票、付款、活动、分类账过账或对账记录使用相同的关联字段。
性能：在连接前按日期筛选源记录，仅选择必需字段，使用连接器分页，启用增量提取，并在支持时对较大的日期范围进行分区。避免反复提取完整历史数据。
数据类型：将时间戳统一为单一时区；在需要审计追溯时保留源时间戳；InvoiceTotalAmount使用decimal类型。
前提条件：ETL或iPaaS许可证必须包含Salesforce连接器；必须为集成用户启用API访问；该用户必须拥有所有已配置数据源所需的对象、字段和记录级权限。
安全性：将凭据存储在平台的密钥管理器中，仅允许授权用户访问提取的数据，并遵守Salesforce及组织对API调用和数据保留的限制。

a 示例查询 config

SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Generated' AS ActivityName,
    CAST(i.[Invoice Created Date field] AS TIMESTAMP) AS EventTime,
    CAST(i.[Invoice Created By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(i.[Invoice Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
WHERE i.[Invoice Number field] IS NOT NULL
  AND i.[Invoice Created Date field] >= [Start date parameter]
  AND i.[Invoice Created Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Submitted for Approval' AS ActivityName,
    CAST(h.[Status Change Date field] AS TIMESTAMP) AS EventTime,
    CAST(h.[Changed By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(h.[New Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Invoice status history object] h ON h.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND h.[New Status field] = 'Pending Approval'
  AND h.[Status Change Date field] >= [Start date parameter]
  AND h.[Status Change Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Approved' AS ActivityName,
    CAST(h.[Status Change Date field] AS TIMESTAMP) AS EventTime,
    CAST(h.[Changed By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(h.[New Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Invoice status history object] h ON h.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND h.[New Status field] = 'Approved'
  AND h.[Status Change Date field] >= [Start date parameter]
  AND h.[Status Change Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Rejected' AS ActivityName,
    CAST(h.[Status Change Date field] AS TIMESTAMP) AS EventTime,
    CAST(h.[Changed By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(h.[New Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Invoice status history object] h ON h.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND h.[New Status field] = 'Rejected'
  AND h.[Status Change Date field] >= [Start date parameter]
  AND h.[Status Change Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Corrected' AS ActivityName,
    CAST(h.[Status Change Date field] AS TIMESTAMP) AS EventTime,
    CAST(h.[Changed By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(h.[New Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Invoice status history object] h ON h.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND h.[Previous Status field] = 'Rejected'
  AND h.[New Status field] = 'Draft'
  AND h.[Status Change Date field] >= [Start date parameter]
  AND h.[Status Change Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Sent to Customer' AS ActivityName,
    CAST(COALESCE(i.[Sent Date field], h.[Status Change Date field]) AS TIMESTAMP) AS EventTime,
    CAST(COALESCE(i.[Sent By field], h.[Changed By field]) AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(COALESCE(h.[New Status field], i.[Invoice Status field]) AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
LEFT JOIN [Invoice status history object] h
  ON h.[Invoice relationship field] = i.[Invoice record identifier field]
 AND h.[New Status field] = 'Sent'
WHERE i.[Invoice Number field] IS NOT NULL
  AND (i.[Sent Date field] IS NOT NULL OR h.[Status Change Date field] IS NOT NULL)
  AND COALESCE(i.[Sent Date field], h.[Status Change Date field]) >= [Start date parameter]
  AND COALESCE(i.[Sent Date field], h.[Status Change Date field]) < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Payment Due Date Reached' AS ActivityName,
    CAST(i.[Payment Due Date field] AS TIMESTAMP) AS EventTime,
    CAST(NULL AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(i.[Invoice Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
WHERE i.[Invoice Number field] IS NOT NULL
  AND i.[Payment Due Date field] IS NOT NULL
  AND i.[Payment Due Date field] >= [Start date parameter]
  AND i.[Payment Due Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Payment Reminder Issued' AS ActivityName,
    CAST(a.[Activity Date field] AS TIMESTAMP) AS EventTime,
    CAST(a.[Assigned User field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(i.[Invoice Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Activity object] a ON a.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND a.[Activity Type field] IN ('Task', 'Email')
  AND a.[Reminder Indicator field] = TRUE
  AND a.[Activity Date field] >= [Start date parameter]
  AND a.[Activity Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Customer Payment Received' AS ActivityName,
    CAST(p.[Payment Received Date field] AS TIMESTAMP) AS EventTime,
    CAST(p.[Recorded By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(i.[Invoice Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Payment object] p ON p.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND p.[Payment Received Date field] IS NOT NULL
  AND p.[Payment Received Date field] >= [Start date parameter]
  AND p.[Payment Received Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Payment Posted to Ledger' AS ActivityName,
    CAST(p.[Ledger Posting Date field] AS TIMESTAMP) AS EventTime,
    CAST(p.[Posted By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(i.[Invoice Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Payment object] p ON p.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND p.[Ledger Posting Date field] IS NOT NULL
  AND p.[Ledger Posting Date field] >= [Start date parameter]
  AND p.[Ledger Posting Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Cash Applied/Reconciled' AS ActivityName,
    CAST(r.[Reconciliation Date field] AS TIMESTAMP) AS EventTime,
    CAST(r.[Reconciled By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(i.[Invoice Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Reconciliation object] r ON r.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND r.[Reconciliation Date field] IS NOT NULL
  AND r.[Reconciliation Date field] >= [Start date parameter]
  AND r.[Reconciliation Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Closed' AS ActivityName,
    CAST(h.[Status Change Date field] AS TIMESTAMP) AS EventTime,
    CAST(h.[Changed By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(h.[New Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Invoice status history object] h ON h.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND h.[New Status field] = 'Closed'
  AND h.[Status Change Date field] >= [Start date parameter]
  AND h.[Status Change Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]
UNION ALL
SELECT
    CAST(i.[Invoice Number field] AS VARCHAR(255)) AS InvoiceNumber,
    'Invoice Written Off' AS ActivityName,
    CAST(h.[Status Change Date field] AS TIMESTAMP) AS EventTime,
    CAST(h.[Changed By field] AS VARCHAR(255)) AS UserResponsible,
    CAST(i.[Billing Department field] AS VARCHAR(255)) AS BillingDepartment,
    CAST(h.[New Status field] AS VARCHAR(255)) AS InvoiceStatus,
    CAST(i.[Invoice Total Amount field] AS DECIMAL(18,2)) AS InvoiceTotalAmount,
    CAST(i.[Payment Due Date field] AS DATE) AS PaymentDueDate
FROM [Invoice object] i
JOIN [Invoice status history object] h ON h.[Invoice relationship field] = i.[Invoice record identifier field]
WHERE i.[Invoice Number field] IS NOT NULL
  AND h.[New Status field] = 'Written Off'
  AND h.[Status Change Date field] >= [Start date parameter]
  AND h.[Status Change Date field] < [End date parameter]
  AND [Company filter]
  AND [Document type filter]

准备开始了吗？

使用此模板开启流程分析，发现显著改善机会。立即开始优化账单和开票流程。

返回改进指南下载模板

加快付款：立即优化O2C账单与开票流程

将账单周期缩短30%，轻松改善现金流。

开始免费试用

无需信用卡，几分钟即可完成设置

您的Order to Cash流程：账单与开票数据模板

您的Order to Cash流程：账单与开票数据模板

订单到收款－开票与发票处理属性

订单到收款－开票与发票处理活动

提取指南

Salesforce报表生成器和数据导出服务

步骤

配置

a 示例查询 config

使用Salesforce REST API的Python脚本

步骤

配置

a 示例查询 python

通过预构建Salesforce连接器使用ETL工具提取

步骤

配置

a 示例查询 config

准备开始了吗？

加快付款：立即优化O2C账单与开票流程

您的Order to Cash流程：账单与开票数据模板

您的Order to Cash流程：账单与开票数据模板

订单到收款－开票与发票处理属性

订单到收款－开票与发票处理活动

提取指南

Salesforce报表生成器和数据导出服务

步骤

配置

a 示例查询 config

使用Salesforce REST API的Python脚本

步骤

配置

a 示例查询 python

通过预构建Salesforce连接器使用ETL工具提取

步骤

配置

a 示例查询 config

准备开始了吗？

加快付款：立即优化O2C账单与开票流程

我们重视您的隐私