Accounting Entry

Structure

The ledger entry type consists of several attributes associated with a ledger entry:

• bundleId: The unique identifier of the batch in which the entry is located. This value is empty as long as the entry is in the “current batch”
• accountEntrySource: Unique identifier of the modified ledger entry (only in the case of a change in entry)
• date: Date of the entry entered by the user in the format dd/mm/yyyy
• dateCreation: Date the entry was created in the format dd/mm/yyyy hh:mm:ss
• exported: Indicates whether the ledger entry has already been exported
• financialPeriod: The accounting year of the entry
  • startDate: Fiscal year start date in format: dd/mm/yyyy
  • endDate: Fiscal year end date in format: dd/mm/yyyy
• ledger: The journal of the accounting entry
  • name: Name of the log
  • code: Log code
• lines: Entry lines in list form
  • labelLine: The label of the writing line
  • accountNumber: The account number. In the case of a business partner line, it corresponds to the number of the business partner account.
  • genericAccountNumber: When the entry line is associated with a business partner account, this value represents the sub-account of the business partner account
  • amount: Amount of the entry line
  • meaning: The direction of the entry line: DEBIT/CREDIT
  • customInformations: List of additional information associated with the entry line
    • id: The unique identifier of the additional information
    • value: The value of this additional information for this line
    • idBinding: The identifier of the index, or value that allows Open Bee™ Scan Capture to auto-populate this value (not be empty)
    • title: The name of the additional information displayed as an accounting entry column.
  • analyticalBreakdown Analytical breakdown. There are 2 types of analytical breakdowns depending on the accounts (they cannot be mixed):
    • Breakdown by plan
    • Breakdown by section
• ID: Internal Unique Identifier of the Entry

Example

{ 
	bundleId: "5e1f383cef15050956fd8f9b",
	accountEntrySource: "2c9c383cef15050956fd5e8d",
	date : "25/01/2020",
	dateCreation : "26/01/2020 15:31:21",
	exported : false,
	financialPeriod : {
		startDate: "01/01/2020",
		endDate: "31/12/2020"
	},
	ledger : {
		name : "Achats",
		code : "ACH"
	},
	lines : [
	{
		labelLine : "Fac Orange 25/01/2020",
		accountNumber : "FORANGE",
		genericAccountNumber : "4010000",
		amount : "20,50",
		meaning : "CREDIT",
		customInformations : [
		{
			id : "f3670cb56fe3d56a95ad8af3",
			value : "256888",
			idBinding : "",
			title : "Colonne libre"
		}, ...],
		analyticalBreakdown: {}
	},
	{
		labelLine : "Fac Orange 25/01/2020",
		accountNumber : "6021000",
		genericAccountNumber : "",
		amount : "17,35",
		meaning : "DEBIT",
		customInformations : [],
		analyticalBreakdown: {}
	}, ...]
	id : "5ad8af3cb56fef36703d56a9"
}

Breakdown by plan

Structure

The breakdown by plan type is made up of a ledger entry line:

• Type: Constant: “VentilatedByPlan”
• ventilatedPlanList: List of broken down plans
  • Plan: Broken Down Analytical Plan
    • Type: Constant “BasicPlan”
    • mandatoryPlan: Indicates whether the plan is required
    • name: Name of the plan
    • code: Plan code
  • lines: Lignes ventilé pour le plan
    • allocatedAmount : Allocated amount
    • Section: Section of the Ventilated Plane
      • name : The name of the section
      • Code : Section code

analyticalBreakdown: {
	type: "VentilatedByPlan",
	ventilatedPlanList : [
	{
		plan : {
			type: "BasicPlan",
			mandatoryPlan: false,
			name: "Service",
			code: "AS-001"
		},
		lines : [
		{
			allocatedAmount: 17.35,
			section: {
			name: "Administratif",
			code: "AS-001-ADM"
		}, ...] 
	},...]
}

Breakdown by section

Structure

The ledger entry type consists of several attributes associated with a ledger entry:

• Type: Constant: “VentilatedBySection”
• multipleVentilatedLines: List of breakdowns
  • allocatedAmount: Allocated amount
  • sectionCombinations: Combination of broken sections
    • groupSectionDetails: Represents the group to which the section belongs
      • name: Name of the group
    • section : Represents the ventilated section
      • name : The name of the section
      • Code : Section code

analyticalBreakdown: {
	type: "VentilatedBySection",
	multipleVentilatedLines: [
	{
		allocatedAmount:17.35,
		sectionCombinations: [
		{
			groupSectionDetails: {
				name: "Service"
			},
			section : {
				name: "Administratif",
				code: "AS-001-ADM"
			}
		},...]
	},...]
}