# Sales Order Bypass Shipment 25.1 Functionality - Accounting

**URL:** <https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438>\
**Category:** Business Applications\
**Tags:** Inventory\
**Created:** [November 6, 2025, 5:57pm UTC](https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438 "2025-11-06T17:57:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alex](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/alex/32/394_2.png) [@alex](https://community.nextw.com/u/alex)\
**Post date:** [November 6, 2025, 5:57pm UTC](https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438/1 "2025-11-06T17:57:38Z")

</div>

Hello, we are testing the new Bypass Shipment Functionality. We have just gotten to the stage where we queue the SO detail to “Ready to Close” - From there, i can see we make a GL entry for the **cost** of the SO line. Is that expected? If I could get in contact with someone who knows the GLs for this new Bypass Shipment functionality, that would be most appreciated. Thanks.

 ![image](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/1X/450c5ab97da81aadae180f3406572c713658d603.jpeg)

---

<div class="post-metadata">

**Author:** ![Sharad](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/sharad/32/136_2.png) [@Sharad](https://community.nextw.com/u/Sharad)\
**Post date:** [November 6, 2025, 6:33pm UTC](https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438/2 "2025-11-06T18:33:54Z")

</div>

That is correct. We write GL entries on the cost side upon Ready to Close using the following GL Mapping Rules:

1. Inventory - for crediting
2. Service Order WIP - for debiting

The cost is credited usually to an inventory account, the corresponding debit is usually to a clearing account.

Upon invoicing, the entry in the cleaning account is reversed and COGS is recorded. In your case, I believe the invoicing happens from the repair order.

---

<div class="post-metadata">

**Author:** ![alex](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/alex/32/394_2.png) [@alex](https://community.nextw.com/u/alex)\
**Post date:** [November 6, 2025, 6:58pm UTC](https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438/3 "2025-11-06T18:58:52Z")

</div>

Awesome, thanks for that info.

Another Q - How would we back-out/Void that transaction? Would we cancel the SO line that is at Ready to close? It doesn’t appear we can delete it from the UI on our side.

---

<div class="post-metadata">

**Author:** ![Sharad](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/sharad/32/136_2.png) [@Sharad](https://community.nextw.com/u/Sharad)\
**Post date:** [November 6, 2025, 7:11pm UTC](https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438/4 "2025-11-06T19:11:12Z")

</div>

You should be able to use the Reopen Sales Order form action or change the workflow on the detail to reopen the detail. That will reverse the transaction.

---

<div class="post-metadata">

**Author:** ![ian.p](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/ian.p/32/427_2.png) [@ian.p](https://community.nextw.com/u/ian.p)\
**Post date:** [November 6, 2025, 7:16pm UTC](https://community.nextw.com/t/sales-order-bypass-shipment-25-1-functionality-accounting/1438/5 "2025-11-06T19:16:10Z")

</div>

@alex if you haven’t already seen it, make sure you check out the post where the feature you’re uptaking was announced:

> [@Internal Will Call Orders](https://community.nextw.com/t/internal-will-call-orders/1306):
>
> [[Internal Will Call Orders Inventory Relief] ](https://vimeo.com/1123902658/3ea5b460da) You can now process Internal Will Call Sales Orders that both bypass shipping and bypass invoicing. See release note InternalWillCallOrdersInventoryRelief25107 for more information. This feature became available in October, 2025 as part of release 25.1.07
