{"id":11100,"date":"2018-01-23T18:14:07","date_gmt":"2018-01-23T12:44:07","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=11100"},"modified":"2023-01-13T14:13:45","modified_gmt":"2023-01-13T08:43:45","slug":"dynamics-365-field-service-payments-related-to-work-order-and-invoice","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2018\/01\/dynamics-365-field-service-payments-related-to-work-order-and-invoice\/","title":{"rendered":"Dynamics 365 Field Service: Payments related to Work Order and Invoice"},"content":{"rendered":"

Introduction:<\/strong><\/h2>\n

Field Service remains a critically important component for most of the organizations. It radically drives customer satisfaction and builds stronger trusted relationship with the customers.<\/p>\n

Recently, while working on field service, we came across an entity \u201cPayments\u201d and \u201cPayment Details\u201d, this created curiosity to explore more on this. And we did some research and play around to find how this entity could be related to work order\/Invoice.<\/p>\n

In this blog, we will discuss, how entities \u2018Payments\u2019 and \u2018Payment Details\u2019 could be related to Work Order and Invoice.<\/p>\n

Payments related to Work Order and Invoice: <\/strong><\/h2>\n

When field service is installed, the user would not be able to see the Payments entity. In order to bring the payment entity in the navigation of work order, the user needs to visit a form editor on work order form -> Add the Payment entity to the navigation of work order and then the payment entity will be ready to use.<\/p>\n

Now let\u2019s have a glance on how Payment section is related to Work Order and Invoice.<\/p>\n

Consider a scenario, create one work order and add a product to it.<\/p>\n

\"Payments<\/p>\n

Now next step is select the product and set the Line Status option as \u201cUsed\u201d.<\/p>\n

\"Payments<\/p>\n

When the work order product\u2019s Line Status changes to \u201cUsed\u201d and work order is \u201cClosed-Posted\u201d, then the Invoice product and also the invoice related to work order is created.<\/p>\n

In order to create invoice record, when the work order is \u201cclosed posted\u201d, the user needs to configure the following field service setting.<\/p>\n

\"Payments<\/p>\n

Now the Total Amount of the work order is \u201c$300\u201d.<\/p>\n

\"Payments<\/p>\n

The invoice created for the work order \u201c00004\u201d and total amount to be paid is \u201c$300\u201d.<\/p>\n

\"Payments<\/p>\n

As we have added the Payment entity in the navigation of work order, click on \u201cPayment\u201d and create a new payment.<\/p>\n

Select the Work Order, Account, Amount, and Payment Type for which the payment should be made. \u00a0\u201cUnapplied Amount\u201d is the calculated field.<\/p>\n

\"Payments<\/p>\n

Now, go to the navigation of the Payment. Here we can find another entity called \u201cPayment Details\u201d.<\/p>\n

Create a new Payment Details. Here we need to select the invoice i.e. invoice for which the payment should be made. If the customer does not pay full amount which is on an invoice, but the customer paid some amount, then let us see how this calculation is done.<\/p>\n

\"Payments<\/p>\n

The total amount was \u201c$300\u201d of the invoice. When the Payment detail was created, the \u201cPayment Amount\u201d paid by the customer is \u201c$50\u201d. Hence, the Amount due on the invoice is \u201c$250\u201d i.e. $300 – $50 = $250.<\/p>\n

Now from this we understand that the total amount on the invoice was \u201c$300\u201d, but the customer paid \u201c$50\u201d and hence amount due i.e. to be paid is \u201c$250\u201d.<\/p>\n

\"Payments<\/p>\n

So if we go and check the \u201cPayment – 00004\u201d in the Payment entity, the \u201cUnapplied amount\u201d field which is a calculated field also shows \u201c$250\u201d.<\/p>\n

\"Payments<\/p>\n

This is how the Payment section works.<\/p>\n

Conclusion:<\/strong><\/h2>\n

The field service has added the Payment section to Work Order and Invoice through which we can calculate the amount due i.e. to be paid by the customer. The Payment section is also used in the Field Service mobile app.<\/p>\n

Need any help with Microsoft Dynamics 365 Field Service module \/ Microsoft CRM \/ Power Platform development?<\/div><\/div><\/h3>\n

Want to manage your field services portal more effectively? Contact us at crm@inogic.com<\/a> and our Inogic- Professional Services Division<\/a> will help you modify, optimize, and automate all our requirements within Microsoft Dynamics 365 Field Service!<\/em><\/p>\n

Happy Servicing!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction: Field Service remains a critically important component for most of the organizations. It radically drives customer satisfaction and builds stronger trusted relationship with the customers. Recently, while working on field service, we came across an entity \u201cPayments\u201d and \u201cPayment Details\u201d, this created curiosity to explore more on this. And we did some research and\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":11101,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,27],"tags":[553],"class_list":["post-11100","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-365","category-field-service-2","tag-dynamics-365-field-service"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/11100","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=11100"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/11100\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/11101"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=11100"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=11100"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=11100"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}