https://community.toasttab.com/t5/restaurant-operations/cash-in-cash-out-transactions-reason-codes/m-p/19247#M8047 <P>Today, Toast requires pre-defined reason codes for Paid Out transactions. However, Cash In/Cash Out transactions only have an 'open comments field,' which essentially makes them impossible to categorize (read: map to GL account) the transactions downstream (e.g., Restaurant 365).</P><P>Is there a way to do any of these:</P><OL class="lia-list-style-type-lower-alpha"><LI>pre-define cash in/cash out categories</LI><LI>disable the comment field altogether</LI><LI>Disable cash out transactions altogether (which would at least force using paid outs)</LI><LI>Enable 'negative' paid outs, to record cash in transactions to a category</LI><LI>Prevent the comments field from feeding through the API into R365</LI></OL> Tue, 13 Oct 2026 20:57:28 GMT nwallace 2026-10-13T20:57:28Z https://community.toasttab.com/t5/restaurant-operations/cash-in-cash-out-transactions-reason-codes/m-p/19247#M8047 <P>Today, Toast requires pre-defined reason codes for Paid Out transactions. However, Cash In/Cash Out transactions only have an 'open comments field,' which essentially makes them impossible to categorize (read: map to GL account) the transactions downstream (e.g., Restaurant 365).</P><P>Is there a way to do any of these:</P><OL class="lia-list-style-type-lower-alpha"><LI>pre-define cash in/cash out categories</LI><LI>disable the comment field altogether</LI><LI>Disable cash out transactions altogether (which would at least force using paid outs)</LI><LI>Enable 'negative' paid outs, to record cash in transactions to a category</LI><LI>Prevent the comments field from feeding through the API into R365</LI></OL> Tue, 13 Oct 2026 20:57:28 GMT https://community.toasttab.com/t5/restaurant-operations/cash-in-cash-out-transactions-reason-codes/m-p/19247#M8047 nwallace 2026-10-13T20:57:28Z