> 持续流程改进 > 订单到收款：账单与发票 > Salesforce Sales Cloud > 数据模板

您的订单到收款流程开票与账单处理数据模板

Salesforce Sales Cloud

← 返回改进指南

订单到收款流程开票与账单处理属性(19) 订单到收款流程开票与账单处理活动(13) 数据提取指南(3)

您的订单到收款流程开票与账单处理数据模板

此模板概述了有效分析订单到收款流程中开票与账单处理所需的关键数据属性和活动，并说明事件日志需要收集哪些具体信息，以及如何提取这些数据。借助此资源，您可以简化流程挖掘工作并获得有价值的洞察。

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

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

下载模板

订单到收款流程开票与账单处理属性

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

3 必填 5 建议填写 11 选填

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

必填建议填写选填

订单到收款流程开票与账单处理活动

以下是建议纳入事件日志的关键流程步骤和里程碑，有助于准确发现流程并评估流程表现。

5 建议填写 8 选填

	活动	说明
	发票已关闭	发票已全额付款并完成核对，生命周期至此结束。这是发票成功处理后的最后一项活动，通常通过状态更新记录。
重要性此活动是流程的主要终点，可用于准确计算端到端周期时间，也为流程分析明确了完成标准。获取途径当Invoice对象的状态字段更新为“已关闭”“已全额付款”或类似终态时，可根据时间戳推断。采集发票状态字段变为最终的“已关闭”状态。事件类型 inferred
	发票已发送给客户	已通过电子邮件、邮寄或门户将获批发票正式送达客户。通常通过填写“发送日期”字段或将状态变为“已发送”来捕获此事件。
重要性这标志着收款期开始，也是计算应收账款周转天数（DSO）的起点。它是跟踪客户沟通和付款时间安排的重要里程碑。获取途径可根据Invoice对象中“发送日期”字段的填写情况，或状态更新为“已发送”来推断。如果通过集成的电子邮件工具发送，也可以从活动历史记录中捕获明确事件。采集 “Sent_Date__c”字段填写时的时间戳。事件类型 inferred
	发票已批准	授权用户已审核并批准发票，确认其准确无误，可以发送给客户。通常在发票状态变为“已批准”时捕获此事件。
重要性这是开票流程中的关键里程碑，决定后续流程能否继续。此处延迟会造成明显瓶颈，影响DSO和整体周期时间；“发票审批周期时间”仪表板会对此进行衡量。获取途径当Invoice对象的状态字段变为“已批准”时，可据此推断。如果使用Salesforce审批流程，也可以从ProcessInstance对象历史记录中明确捕获此事件。采集发票状态字段变为“已批准”，或正式审批流程步骤完成。事件类型 inferred
	收到客户付款	客户已支付发票款项，资金已到账。通常通过创建关联的“Payment”记录并将其与发票关联来记录。
重要性这是收款流程中最重要的里程碑，也是计算DSO的终点，标志着收入已成功收回。获取途径根据与Invoice对象关联的“Payment”自定义对象记录的创建日期捕获。也可以根据发票状态变为“已付款”推断。采集创建关联的Payment记录。事件类型 explicit
	生成发票	此活动表示在Salesforce中创建了新的发票记录，是特定交易开票流程的正式起点，通常发生在订单履行完毕或达到合同里程碑之后。该事件根据发票记录的创建时间戳捕获。
重要性这是开票流程的主要开始事件。分析从此时到收到付款的时间，有助于衡量订单到收款的整体周期时间，并发现初始数据录入延迟。获取途径此事件根据Salesforce中发票自定义对象或类似发票对象的创建日期（CreatedDate字段）捕获。采集发票对象记录的创建时间戳。事件类型 explicit
	付款已过账至分类账	收到的付款已正式记录在公司的财务系统或分类账中。集成运行后，可能会通过付款或发票记录的状态更新来捕获此事件。
重要性此活动将收到付款与完成财务核对区分开来。收款到过账之间的时间可以揭示内部会计流程中的延迟。获取途径当Payment或Invoice对象的状态字段变为“已过账”或“已导出至ERP”等值时，可据此推断；该字段通常通过API集成更新。采集付款或发票状态变为“已过账”。事件类型 inferred
	发票已更正	表示发票被拒绝或发现错误后进行的人工更正或更新。通常可根据发票状态回退到先前状态来推断，例如从“已拒绝”变回“草稿”。
重要性识别更正循环对于衡量“发票返工率”KPI至关重要。大量更正表明发票初始生成环节存在问题，可能导致延误。获取途径通过字段历史记录推断：检测状态是否从后续阶段（如“已拒绝”“已批准”）回退到较早阶段（如“草稿”“处理中”）。采集发票状态在流程中回退。事件类型 inferred
	发票已核销	已决定免除债务，发票未全额付款即关闭。这代表开票流程以未成功的替代路径结束。
重要性跟踪核销有助于量化收入损失，并识别导致坏账的客户或情形。这是需要关注的关键异常路径，对评估财务状况十分重要。获取途径当Invoice对象的状态字段更新为“已核销”或“已取消－坏账”时，可根据时间戳推断。采集发票状态字段变为“已核销”。事件类型 inferred
	发票被拒绝	审批人拒绝了发票，通常是因为存在错误或差异，需要更正后重新提交。此事件通过发票记录的状态变为“已拒绝”来捕获。
重要性此活动表示发生了返工，流程效率受到影响。分析拒绝频率有助于找出常见错误来源，并支持“开票流程返工与错误”仪表板中的根因分析。获取途径当Invoice对象的状态字段变为“已拒绝”时，可据此推断。正式审批流程历史记录中的评论也可能包含相关数据。采集发票状态字段变为“已拒绝”。事件类型 inferred
	已发送付款提醒	已向客户发送通知，提醒其即将到期或已逾期的付款。通常会记录为与发票关联的活动（Task或Email）记录。
重要性跟踪提醒有助于评估催收策略的效果，也是“付款提醒效果”仪表板和“付款提醒触发率”KPI的重要依据。获取途径根据与Invoice对象相关的活动（Task或Email）记录创建情况捕获；主题或类型需表明该活动是付款提醒。采集创建关联的Task或Email记录，且记录具有特定类型或主题。事件类型 explicit
	提交发票以供审批	发票已定稿，并提交内部审核，之后才会发送给客户。通常通过发票记录的状态字段变化来捕获此活动，例如从“草稿”变为“待审批”。
重要性跟踪此活动有助于单独衡量发票在审批队列中的停留时间，也是计算“平均发票审批时间”KPI的关键第一步。获取途径通过Invoice对象的字段历史记录推断：当状态字段更新为“已提交审批”或“审核中”等值时，即可识别此事件。采集发票状态字段变为“待审批”。事件类型 inferred
	现金已核销／已核对	收到的付款已在系统中与对应发票完全匹配并核销，应收账款随之结清。此事件通过付款或发票记录的最终状态变化捕获。
重要性这标志着现金转换周期的最后一步。“付款核对绩效”仪表板依靠此活动衡量财务团队的收款入账效率。获取途径当Invoice对象或关联的Payment对象状态变为“已核对”或“已应用”等终态时，可据此推断。采集发票或付款状态变为“已核对”。事件类型 inferred
	达到付款到期日	这是一个计算得出的事件，表示根据发票付款条款应付款项到期的时间。它不是用户操作，而是根据发票数据推导得出。
重要性此活动为分析付款行为和衡量“按时付款率”KPI提供了重要基准，有助于区分按时付款和逾期付款。获取途径这是一个计算得出的事件，通过将当前时间戳与Invoice对象中的“到期日”字段进行比较得出。它不是Salesforce中存储的事件。采集将当前日期与发票的到期日字段进行比较后计算得出。事件类型 calculated

建议填写选填

数据提取指南

如何从Salesforce Sales Cloud获取数据

步骤

检查前提条件：确认您在Salesforce中拥有所需权限，包括“运行报表”“创建和自定义报表”及“导出报表”。确认Invoice和Payment对象的关键状态字段已启用字段历史跟踪。操作方法：进入Setup > Object Manager，找到相关对象，打开Fields & Relationships，然后点击“Set History Tracking”。
制定报表方案：由于活动来自不同记录或事件（例如创建发票、状态变更和关联付款），因此需要创建多份报表。您需要为每种不同的数据来源分别创建报表，再在外部合并结果。
创建记录生成报表：先处理最简单的事件。为“发票已生成”和“收到客户付款”创建报表。进入Reports选项卡并点击“New Report”。选择包含Invoice对象（例如“Invoices”）或Payment对象的报表类型。添加与事件日志属性对应的列。对于“发票已生成”活动，发票记录的CreatedDate就是EventTime。
创建字段历史报表：如需记录“发票已提交审批”“发票已批准”“发票已拒绝”和“发票已更正”等状态变更，请基于“Invoice History”报表类型创建报表。此特殊报表类型会显示字段历史跟踪记录的变更。请筛选此报表，只显示Status字段的变更。
创建基于日期的事件报表：对于“已向客户发送发票”或“已到付款到期日”等事件，请基于Invoice对象创建报表。使用日期字段本身（例如Sent_Date__c或Payment_Due_Date__c）作为EventTime。您必须筛选出这些日期不为空的记录。
创建关联活动报表：对于“已发送付款提醒”等事件，您需要创建一份将活动（Tasks或Events）与Invoice关联起来的报表。使用“Activities with Invoices”等报表类型，或创建自定义报表类型。筛选出主题或类型表明属于提醒的活动。
为所有报表添加标准列：请确保每份报表都包含可映射到所需事件日志结构的列：InvoiceNumber、EventTime字段（例如CreatedDate或字段变更日期）、UserResponsible（例如LastModifiedById）以及其他建议的属性。
将报表导出为CSV：分别运行每份报表。在报表结果页面中，使用下拉菜单选择“Export”，然后选择“Details Only”格式并使用.csv扩展名。对创建的所有报表重复此操作。
合并并转换数据：在电子表格程序中打开导出的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）。
数据导出服务：您也可以使用Salesforce内置的数据导出服务（Setup > Data Export），代替逐份运行报表。该服务每周或每月导出组织的全部数据，可用于完整备份，但之后需要进行大量处理，才能筛选、关联和转换数据，生成事件日志。
用户权限：执行数据提取的用户需要拥有所有相关对象（例如Account、Order、Invoice__c、Payment__c和Activity）及字段的读取权限，以及创建和导出报表的权限。

查询示例 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”选项。
启用字段历史跟踪：以管理员身份登录Salesforce组织。依次打开“Setup”和“Object Manager”。找到主要发票对象，例如Invoice__c，然后打开“Fields & Relationships”。点击“Set History Tracking”，启用发票状态字段的跟踪，例如Status__c。对付款对象（例如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文件包含必需列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字段历史跟踪。如果当时未启用，就无法捕获历史变更。
API调用限制：Salesforce会限制24小时内可进行的API调用次数。对于超大型数据集，可考虑按较短日期范围分批提取，或安排在非高峰时段运行，以避免触及限制。

查询示例 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应使用十进制类型。
前提条件：ETL或iPaaS许可证必须包含Salesforce连接器；集成用户必须启用API访问，并拥有所有已配置数据源所需的对象、字段和记录级权限。
安全：将凭据存储在平台的机密管理器中，限制提取数据的访问权限，并遵守Salesforce及组织对API调用和数据保留的限制。

查询示例 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]

准备好开始了吗？

使用此模板启动流程分析，发现显著的改进机会。立即开始优化开票流程。

返回改进指南

下载模板

加快收款：立即优化订单到收款开票流程

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

开始免费试用

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

您的订单到收款流程开票与账单处理数据模板

您的订单到收款流程开票与账单处理数据模板

订单到收款流程开票与账单处理属性

订单到收款流程开票与账单处理活动

数据提取指南

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

步骤

配置

查询示例 config

使用Salesforce REST API的Python脚本

步骤

配置

查询示例 python

通过预置Salesforce连接器使用ETL工具提取数据

步骤

配置

查询示例 config

准备好开始了吗？

加快收款：立即优化订单到收款开票流程