Service - CommerceAccounting Sale - Revision history

Sven the Barbarian: /* Object Schemas */

2026-01-21T15:22:21Z

Object Schemas

← Older revision		Revision as of 15:22, 21 January 2026
Line 15:		Line 15:
	canDelete: false,		canDelete: false,
	belongTo: {		belongTo: {
	serviceTag: "~~User~~",		serviceTag: "ComAccLink",
	objectType: "~~user~~"		objectType: "comAccLink"
	},		},
	addOnDataStructure: [],		addOnDataStructure: [],

Sven the Barbarian at 13:59, 12 January 2026

2026-01-12T13:59:29Z

← Older revision		Revision as of 13:59, 12 January 2026
Line 46:		Line 46:
	= flowSchemas =		= flowSchemas =

	== ~~saleCreated~~ ==		== saleCommitted ==

	* when creating a sale, iterate saleLineItems to decide which journal entries are created		* when creating a sale, iterate saleLineItems to decide which journal entries are created

Sven the Barbarian at 15:04, 11 January 2026

2026-01-11T15:04:28Z

← Older revision		Revision as of 15:04, 11 January 2026
Line 73:		Line 73:
	* all credit side may have:		* all credit side may have:
	*# (credit)salesTaxPayable(Liability)		*# (credit)salesTaxPayable(Liability)
			*# (credit)vatPayable(liability)

	=== Goods Sold ===		=== Goods Sold ===

Sven the Barbarian at 15:01, 11 January 2026

2026-01-11T15:01:51Z

← Older revision		Revision as of 15:01, 11 January 2026
Line 106:		Line 106:
	* same as an Asset, except use the term Amortization instead of Depreciation, which are functionally the same		* same as an Asset, except use the term Amortization instead of Depreciation, which are functionally the same

	== ~~inventoryGoodsPurchaseChange~~ ==		== saleChange ==

	* make adjustment to journal entries when saleLineItemId changes		* make adjustment to journal entries when saleLineItemId changes

Sven the Barbarian at 13:29, 11 January 2026

2026-01-11T13:29:43Z

← Older revision		Revision as of 13:29, 11 January 2026
Line 38:		Line 38:

	* one saleId may link to multiple journalIds, sale value and inventory adjustment entries		* one saleId may link to multiple journalIds, sale value and inventory adjustment entries
	* maintains a link between saleId and journalIds, so can adjust if changes made to ~~purchases~~		* maintains a link between saleId and journalIds, so can adjust if changes made to sale

	== Relationships ==		== Relationships ==

Sven the Barbarian at 13:27, 11 January 2026

2026-01-11T13:27:27Z

← Older revision		Revision as of 13:27, 11 January 2026
Line 1:		Line 1:
	= Overview =		= Overview =

	Handle sales in one service, ~~and~~ some Accounting entries include the full amount, some break up according to saleLineItems.		Handle sales in one service, because some Accounting entries include the full amount, some break up according to saleLineItems.

	= Repository =		= Repository =

Sven the Barbarian at 13:22, 11 January 2026

2026-01-11T13:22:56Z

← Older revision		Revision as of 13:22, 11 January 2026
Line 49:		Line 49:

	* when creating a sale, iterate saleLineItems to decide which journal entries are created		* when creating a sale, iterate saleLineItems to decide which journal entries are created
			* accountsReceivable accountId will need to come from [[Service - CommerceAccounting Customer]]

	=== Sale Value ===		=== Sale Value ===

Sven the Barbarian: /* Intangible Assets */

2026-01-11T13:14:19Z

Intangible Assets

← Older revision		Revision as of 13:14, 11 January 2026
Line 103:		Line 103:
	=== Intangible Assets ===		=== Intangible Assets ===

	* same as an Asset, except use Amortization instead of Depreciation		* same as an Asset, except use the term Amortization instead of Depreciation, which are functionally the same

	== inventoryGoodsPurchaseChange ==		== inventoryGoodsPurchaseChange ==

Sven the Barbarian at 13:10, 11 January 2026

2026-01-11T13:10:54Z

← Older revision		Revision as of 13:10, 11 January 2026
Line 55:		Line 55:
	*# (debit)accountsReceivable(Asset)		*# (debit)accountsReceivable(Asset)

	* The other side (credit) is broken up depending on goods or assets		* The other side (credit) is broken up depending on goods/service or assets

	* For goods value an entry is entered into the below		* For goods value an entry is entered into the below
	*# (credit)~~sales~~(Revenue)		*# (credit)goodsSale/serviceSale(Revenue)

	* Assets have:		* Assets have:
Line 65:		Line 65:
	*# (debit or credit)creditGainOnSale(Renenue)/debitLossOnSale(Expense)		*# (debit or credit)creditGainOnSale(Renenue)/debitLossOnSale(Expense)

	* ~~both goods and assets~~ may have:		* Intangible Assets have:
			*# (credit)inventoryIntangibleAsset(Asset)
			*# (debit)accumulatedAmortization(Asset)
			*# (debit or credit)creditGainOnSale(Renenue)/debitLossOnSale(Expense)

			* all credit side may have:
	*# (credit)salesTaxPayable(Liability)		*# (credit)salesTaxPayable(Liability)

Line 86:		Line 91:
	* will need to query Accounting Assets service for depreciation amount		* will need to query Accounting Assets service for depreciation amount
	* may need to query ComAcc Inventory service to find link between Commerce Asset and Accounting Asset, so can find depreciation		* may need to query ComAcc Inventory service to find link between Commerce Asset and Accounting Asset, so can find depreciation

			=== Services Sold ===

			* no additional entries required

			=== Intangible Goods Sold ===

			* no additional entries required
			* entries same as physical Goods

			=== Intangible Assets ===

			* same as an Asset, except use Amortization instead of Depreciation

	== inventoryGoodsPurchaseChange ==		== inventoryGoodsPurchaseChange ==

Sven the Barbarian: Created page with "= Overview = Handle sales in one service, and some Accounting entries include the full amount, some break up according to saleLineItems. = Repository = ... = Object Schemas = ; Additional Information: Per Service Schemas { objectType: "comAccSaleLink", canDelete: false, belongTo: { serviceTag: "User", objectType: "user" }, addOnDataStructure: [], storageResources: { "dynamo": { "storageType": "dynamoDB", "tab..."

2026-01-11T12:21:03Z

Created page with "= Overview = Handle sales in one service, and some Accounting entries include the full amount, some break up according to saleLineItems. = Repository = ... = Object Schemas = ; Additional Information: Per Service Schemas <syntaxhighlight lang="JavaScript"> { objectType: "comAccSaleLink", canDelete: false, belongTo: { serviceTag: "User", objectType: "user" }, addOnDataStructure: [], storageResources: { "dynamo": { "storageType": "dynamoDB", "tab..."

New page

= Overview =

Handle sales in one service, and some Accounting entries include the full amount, some break up according to saleLineItems.

= Repository =

...

= Object Schemas =
; Additional Information: [[Per Service Schemas]]

<syntaxhighlight lang="JavaScript">
{
objectType: "comAccSaleLink",
canDelete: false,
belongTo: {
serviceTag: "User",
objectType: "user"
},
addOnDataStructure: [],
storageResources: {
"dynamo": {
"storageType": "dynamoDB",
"tableName": "comAccSaleLink",
}
},
fieldNames: {
// probably have two dynamo tables, one identified by saleId, one by journalId

},
identifiers: [
{
// see above note
}
]
}
</syntaxhighlight>

* one saleId may link to multiple journalIds, sale value and inventory adjustment entries
* maintains a link between saleId and journalIds, so can adjust if changes made to purchases

== Relationships ==

...

= flowSchemas =

== saleCreated ==

* when creating a sale, iterate saleLineItems to decide which journal entries are created

=== Sale Value ===

* the total sale value has journal entry for all the below:
*# (debit)accountsReceivable(Asset)

* The other side (credit) is broken up depending on goods or assets

* For goods value an entry is entered into the below
*# (credit)sales(Revenue)

* Assets have:
*# (credit)inventoryAsset(Asset)
*# (debit)accumulatedDepreciation(Asset)
*# (debit or credit)creditGainOnSale(Renenue)/debitLossOnSale(Expense)

* both goods and assets may have:
*# (credit)salesTaxPayable(Liability)

=== Goods Sold ===

* the total saleLineItem value for Inventory Goods has a journal entry for:
*# (debit)cogsGoods(Expense)
*# (credit)inventoryGoods(Asset)

=== Raw Material Sold ===

* the total saleLineItem value for Inventory Raw Materials has a journal entry for:
*# (debit)cogsRawMaterial(Expense)
*# (credit)inventoryRawMaterial(Asset)

=== Assets Sold ===

* might not have accumulatedDepreciation applied yet
* if sold for same amount as original value then not have creditGainOnSale/debitLossOnSale
* will need to query Accounting Assets service for depreciation amount
* may need to query ComAcc Inventory service to find link between Commerce Asset and Accounting Asset, so can find depreciation

== inventoryGoodsPurchaseChange ==

* make adjustment to journal entries when saleLineItemId changes
* perhaps handling removal of sale/journal entries, or creation of new entries
* basically re-calculate all entries and check against existing

= Working documents =

[[:Category:Working_documents - CommerceAccounting Sale| CommerceAccounting Sale]]

[[Category:Backend services| CommerceAccounting Sale]]