> ## Documentation Index > Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt > Use this file to discover all available pages before exploring further. # Update account (v1) > Update an account identified by its number. Send the same fields as create. Omit `monetary_distinction` and `is_monetary` to keep the stored monetary distinction. Send `null` for `allowed_company_ids` to remove company restrictions. A system account accepts only the fields the app update accepts. A change to monetary distinction is refused when the account has posted transactions. **Side effects** * If an approval workflow matches this request, DualEntry can set `is_active` to `false`. ## OpenAPI ````yaml /developers/openapi/resources-v1.json put /public/v1/accounts/{account_number}/ openapi: 3.1.0 info: title: DualEntry Public API version: 1.0.0 description: '' servers: - url: https://api.dualentry.com description: Production environment security: [] tags: - name: Health description: >- Monitor API availability and service status. Use these endpoints to verify connectivity and check if the API is operational. - name: Webhooks description: >- Register webhook endpoints to receive real-time event notifications when records change in your organization. Manage subscriptions, view available topics, and inspect delivery history. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Accounts description: >- Manage your chart of accounts. Create and maintain the accounts used to categorize financial transactions, including assets, liabilities, equity, revenue, and expenses. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Reporting description: >- Reporting facts and balances: account balances as of a date; paginated general-ledger lines; dense trial-balance facts (account x company x month); chart-of-accounts facts; and consolidated rates. Row shapes match the `general_ledger`, `trial_balance`, `chart_of_accounts`, and `consolidated_rates` tables in your data export. - name: Budgets description: >- Read income statement and balance sheet budget settings. Monthly cell values, actuals comparisons, and accounts are available through separate budget routes. - name: Companies description: >- Access and manage company information. Retrieve details about your organization including legal name, tax identifiers, addresses, and accounting preferences. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Period Locks description: >- Period locks for bills, invoices, other ledger activity, non-ledger records, and tax schedules. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Payment Methods description: >- List payment methods. Filter by id to resolve payment_method_id on a payment record. V2 API only. - name: Terms description: >- List payment terms. Use a term `id` as `term_id` on a record that has a due date. - name: Books description: >- List accounting books. Use book ids in `book_ids` on a journal entry. Depreciation books are a separate resource. - name: Projects description: >- List projects. Use a project `id` as `billable_project_id` on a billable line. - name: Contract Templates description: >- List contract templates. Use a template `id` as `contract_template_id` on a contract. - name: Accrual Templates description: >- List accrual templates. Use a template `id` as `accrual_template_id` on a journal entry. - name: Paper Check Templates description: >- List paper check templates. Use a template `id` as `template_id` when you print a check. - name: Customers description: >- Manage customer records. Create, update, and track customers who purchase goods or services from your organization, including contact information, billing addresses, and payment terms. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Contracts description: >- Manage revenue recognition contracts. Create, retrieve, and update contracts with performance obligations, manage obligation usage, and create change orders (v2). If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Items description: >- Manage products and services. Define items that appear on invoices and bills, including pricing, descriptions, and associated accounts for revenue or expense tracking. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Vendors description: >- Manage vendor and supplier records. Track businesses and individuals from whom you purchase goods or services, including contact details, payment terms, and tax information. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Journal Entries description: >- Create and manage manual journal entries. Create and update post a general ledger transaction. A reversal date posts a reversing transaction. Book ids assign accounting books. An aging reason on an accounts receivable or accounts payable line excludes that line from aging. The save can link a related journal entry and an accrual template. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Invoices description: >- Manage sales invoices. Create and track invoices sent to customers for goods or services rendered, including line items, taxes, discounts, and payment status. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Quotes description: >- Create, submit, and send CPQ quotes, with line billing frequencies, multi-year ramps, recipients and signing order, and totals by billing frequency. Requires the CPQ subscription. Save a quote with `record_status` `posted` to submit it for approval. Approvers approve or reject it in DualEntry. Send your own quote PDF. This API does not render one. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Sales Orders description: >- Create and manage sales orders. Track customer orders for goods or services before invoicing, including line items, quantities, fulfillment status, and invoicing progress. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Bills description: >- Manage vendor bills and payables. Record and track bills received from vendors for goods or services purchased, including line items, due dates, and payment tracking. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Customer Prepayments description: >- Track advance payments from customers. Access prepayments received before goods or services are delivered, which can be applied to future invoices. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Customer Prepayment Applications description: >- Apply customer prepayments and credits to invoices. Record applications of prepayments or credit memos to reduce invoice balances. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Customer Deposits description: >- Manage customer deposit transactions. Record and track deposits received from customers as security or partial payment, held in liability accounts until earned or refunded. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Customer Refunds description: >- Process and track customer refunds. Record refunds issued to customers for overpayments, returns, or cancelled transactions. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Customer Credits description: >- Manage credit memos for customers. Issue credits for returned goods, billing adjustments, or discounts that reduce customer balances or can be applied to future invoices. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Cash Sales description: >- Record immediate cash sales transactions. Track sales where payment is received at the time of sale, including point-of-sale transactions and cash receipts. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Customer Payments description: >- Record and manage customer payments. Track payments received from customers and apply them to outstanding invoices, including partial payments and overpayments. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Recurring Invoices description: >- Automate recurring billing. Set up and manage templates for invoices that are automatically generated on a regular schedule (e.g., monthly subscriptions). If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Recurring Bills description: >- Automate recurring expenses. Configure templates for bills that repeat on a regular basis (e.g., monthly rent, subscriptions) to streamline expense tracking. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Recurring Journal Entries description: >- Automate recurring journal entries. Create templates for journal entries that occur regularly (e.g., monthly depreciation, amortization) to ensure consistent accounting treatment. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Classifications description: >- Manage custom classification dimensions. Create and maintain classification categories (e.g., departments, locations, projects) used to tag and analyze transactions across multiple dimensions. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Classifications Lines description: >- Manage classification values. Define the specific values within each classification category that can be assigned to transaction line items for detailed reporting and analysis. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Custom Fields description: >- Manage custom field definitions. Extend records with organization-specific attributes: name, type (text, number, boolean, date, single_select, multi_select, currency, link, paragraph), default value, options, and which record types (invoice, bill, customer, vendor, etc.) and companies the field applies to. Values are set via the `custom_fields` attribute on each record's create/update endpoint. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Purchase Orders description: >- Create and track purchase orders. Manage formal requests to vendors for goods or services, including approval workflows, receiving tracking, and bill matching. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Vendor Payments description: >- Record vendor payments and apply them to bills, vendor credits, and journal entry lines. Create and update post a general ledger transaction. The save also computes realized, rounding, and matching gain or loss. Send attachments to replace the file list. `PATCH` changes only the sent fields. `POST /{number}/attachments/` adds files and keeps existing files. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Vendor Prepayments description: >- Track advance payments to vendors. Record prepayments made before goods or services are received, which can be applied to future bills. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Vendor Prepayment Applications description: >- Apply vendor prepayments to bills. Record applications of prepayments to reduce bill balances and track amounts owed. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Vendor Credits description: >- Manage vendor credit memos. Record credits from vendors for returned goods, billing adjustments, or discounts that reduce amounts owed or can be applied to future bills. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Vendor Refunds description: >- Process and track vendor refunds. Record refunds received from vendors for overpayments, returns, or cancelled transactions. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Paper Checks description: >- Manage paper check printing. Create, queue, and batch print paper checks for vendor payments, direct expenses, vendor prepayments, and customer refunds. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Direct Expenses description: >- Record direct expense transactions. Track payments made directly from a bank or credit card account for expenses, without going through the accounts payable process. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Bank Transfers description: >- Manage bank-to-bank transfers. Record and track transfers between bank and credit card accounts, including multi-currency transfers with exchange rate handling. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Bank Match description: >- Reconcile bank-feed rows against accounting transactions. List bank rows, trigger the matching pipeline, read AI suggestions, and confirm or undo matches. V2 API only. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Bank Connections description: >- Register and list customer-built inbound bank connection feeds. Create connections and accounts with `customer_api` as `source_type`, then push transactions separately. V2 API only. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Fixed Assets description: >- Manage fixed assets and capital equipment. Create, update, and track long-lived tangible assets including depreciation schedules, account assignments, and asset lifecycle management. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Fixed Asset Classes description: List fixed asset classes used to set `fixed_asset_class_id` on an asset. - name: Intercompany Journal Entries description: >- Create and manage intercompany journal entries. Record GL activity that spans two or more companies within the same organization, with per-line company assignment and automatic intercompany elimination. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Depreciation Books description: >- Discover available depreciation books for multi-book depreciation. Each organization has a posting book (BOOK) and may have additional tax books (FEDERAL, AMT, STATE_*). V2 API only. - name: VAT Rates description: >- Look up available VAT (Value Added Tax) rates for your organization. Use these IDs as `vat_rate_id` on transaction line items. Rates are scoped by country and include standard, reduced, zero-rated, exempt, and reverse charge types. V2 API only. - name: GST Tax Rates description: >- Look up available GST (Goods and Services Tax) rates for your organization. Use these IDs as `gst_tax_rate_id` on transaction line items. Covers AU, NZ, SG, IN, CA GST regimes and MY SST, with per-component breakdowns (e.g. CGST+SGST for India). V2 API only. - name: Product Tax Codes description: >- Manage organization product tax codes and discover global product tax codes. Use these IDs as `product_tax_code_id` on item payloads. V2 API only. - name: Approval Policies description: >- Manage approval workflows and policies. Define approval rules, steps, conditions, and approvers for different record types. Monitor workflow execution states and view approval history. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Inbox description: >- View pending approvals and approval status. Access transactions and records awaiting approval across the organization, including full approval workflow details, approvers, and action history. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: Statistical Journals description: >- Record non-monetary quantity values, such as headcount or square footage. Statistical journals never post to the general ledger. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. - name: E-invoicing description: >- Read the e-invoicing settings of the organization, the registrations of its companies, and the e-invoice filing of an invoice or a customer credit with its events and legal files. Retry a failed filing, refresh a started one, check a customer before a post, and set the e-invoicing identifiers of a customer. The settings, the registrations and the company identifiers are read-only: change them in the DualEntry app. **Subscription.** Every route except the status route needs the e-invoicing subscription. Without it, the route answers `402` before it checks the permission. The filing, its legal files and the send rules of a record that DualEntry filed still answer after the subscription ends. An organization without the subscription posts, sends and archives invoices as before. **Permissions.** The settings, the registrations and the event list need `e_invoicing:view`. The filing of a record follows the permission of its record: `invoice:view` or `customer_credit:view` to read it, `invoice:edit` or `customer_credit:edit` to retry it. The identifiers need `e_invoicing:view` with `customer:view` or `vendor:view` to read, and `e_invoicing:edit` with `customer:edit` to write, as in the app. A key that the CLI sign-in made reaches only the companies of its user. **Error codes.** A refused e-invoicing request carries a stable `error_code`: - `e_invoicing_send_held`: the authority must clear the invoice before the customer gets it. - `e_invoicing_legal_pdf_missing`: the authority PDF is not stored yet. - `e_invoicing_validation`: the authority refuses the document data. - `e_invoicing_setup`: the setup of the country is broken. - `e_invoicing_engine`: the e-invoicing engine did not answer or refused the request. - `e_invoicing_not_retryable`: the filing is not failed or rejected. - `e_invoicing_error`: any other refusal. A record save that e-invoicing refuses, such as a change of a cleared invoice, answers `422` with the reason under the `e_invoicing` key. Not in v1. - name: Data Exports description: >- Request off-cycle refreshes of your organization's data export to its configured destination (for example a Snowflake warehouse) and poll their status. Exports also run automatically on a schedule; these requests are an on-demand supplement. Requests are accepted and orchestrated by DualEntry; there is no SLA on when a run starts. If your organization connects an integration that syncs this resource with a third-party system, a change you make here can also be applied in that system, immediately or on a later sync. See the documentation for each integration for details. paths: /public/v1/accounts/{account_number}/: put: tags: - Accounts summary: Update account description: >- Update an account identified by its number. Send the same fields as create. Omit `monetary_distinction` and `is_monetary` to keep the stored monetary distinction. Send `null` for `allowed_company_ids` to remove company restrictions. A system account accepts only the fields the app update accepts. A change to monetary distinction is refused when the account has posted transactions. **Side effects** - If an approval workflow matches this request, DualEntry can set `is_active` to `false`. operationId: core_api_public_accounts_update_account parameters: - in: path name: account_number schema: title: Account Number type: integer required: true - name: Idempotency-Key in: header required: false schema: type: string maxLength: 255 description: >- Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns `422`. requestBody: content: application/json: schema: $ref: '#/components/schemas/PublicAccountSchemaUpdateIn' required: true responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/PublicAccountSchemaOut' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/ErrorSchema' '422': description: Unprocessable Content content: application/json: schema: $ref: '#/components/schemas/ErrorSchema' '500': description: Internal Server Error content: application/json: schema: $ref: '#/components/schemas/ErrorSchema' '503': description: Service Unavailable content: application/json: schema: $ref: '#/components/schemas/ErrorSchema' components: schemas: PublicAccountSchemaUpdateIn: properties: account_type: $ref: '#/components/schemas/AccountType' bank_routing: title: Bank Routing maxLength: 9 type: - string - 'null' iban: title: Iban type: - string - 'null' name: maxLength: 256 minLength: 2 title: Name type: string description: default: '' maxLength: 512 title: Description type: string number: maximum: 9223372036854776000 minimum: 1 title: Number type: integer currency_iso_4217_code: anyOf: - $ref: '#/components/schemas/SystemCurrencies' - type: 'null' is_active: title: Is Active type: boolean company_id: title: Company Id type: - integer - 'null' parent_account_id: title: Parent Account Id type: - integer - 'null' category_1099: anyOf: - $ref: '#/components/schemas/Category1099' - const: '' type: string default: '' title: Category 1099 allowed_company_ids: description: >- Company IDs allowed to use this account in transactions. Restricts a shared chart-of-accounts entry to specific entities within your organization. Omit for no company restrictions (bank and credit card accounts use company_id instead). example: - 101 - 102 title: Allowed Company Ids items: type: integer type: - array - 'null' is_monetary: description: >- Legacy boolean for monetary distinction. Omit this field and `monetary_distinction` to keep the stored value. title: Is Monetary type: - boolean - 'null' monetary_distinction: anyOf: - $ref: '#/components/schemas/MonetaryDistinction' - type: 'null' description: >- Whether the account is monetary or non-monetary. Send `monetary` or `non_monetary`. Omit this field and `is_monetary` to keep the stored value. A change is refused when the account has posted transactions. bank_alias: title: Bank Alias maxLength: 256 type: - string - 'null' bank_account_number: title: Bank Account Number maxLength: 20 minLength: 1 type: - string - 'null' start_bank_match_date: title: Start Bank Match Date format: date type: - string - 'null' default_classification_line_ids: title: Default Classification Line Ids items: type: integer type: - array - 'null' required: - account_type - name - number - currency_iso_4217_code - is_active - parent_account_id title: PublicAccountSchemaUpdateIn type: object PublicAccountSchemaOut: properties: created_at: description: Date and time the record was created format: date-time title: Created At type: string updated_at: description: Date and time the record was last updated format: date-time title: Updated At type: string created_by: anyOf: - $ref: '#/components/schemas/AuditActorSchemaOut' - type: 'null' updated_by: anyOf: - $ref: '#/components/schemas/AuditActorSchemaOut' - type: 'null' approval_status: title: Approval Status type: - string - 'null' next_approvers: title: Next Approvers items: $ref: '#/components/schemas/ApproverDictSchema' type: - array - 'null' rejected_by: anyOf: - $ref: '#/components/schemas/RejectedBySchema' - type: 'null' id: title: Id type: integer name: title: Name type: string number: title: Number type: integer description: title: Description type: string is_active: title: Is Active type: boolean is_system: title: Is System type: boolean company_id: title: Company Id type: - integer - 'null' parent_account_id: title: Parent Account Id type: - integer - 'null' account_type: $ref: '#/components/schemas/AccountType' currency_iso_4217_code: anyOf: - $ref: '#/components/schemas/SystemCurrencies' - type: 'null' description: >- The ISO 4217 code of the currency of the account. Only available for bank type accounts. category_1099: anyOf: - $ref: '#/components/schemas/Category1099' - const: '' type: string title: Category 1099 system_ref: anyOf: - $ref: '#/components/schemas/SystemAccountNames' - type: 'null' monetary_distinction: enum: - monetary - non_monetary title: Monetary Distinction type: string default_classification_line_ids: title: Default Classification Line Ids items: type: integer type: - array - 'null' required: - created_at - updated_at - id - name - number - description - is_active - is_system - company_id - parent_account_id - account_type - currency_iso_4217_code - category_1099 - system_ref - monetary_distinction title: PublicAccountSchemaOut type: object ErrorSchema: properties: success: const: false default: false title: Success type: boolean errors: additionalProperties: items: type: string type: array title: Errors type: object error_code: description: >- A stable code that identifies the control that refused the request. Branch on this code, not on the message text. When a control refuses the request, `error_code` is one of these values: - `period_locked`: The request changes data in a locked accounting period. - `approved_record_immutable`: The record is approved, and the organization does not allow changes to approved records. - `posted_record_immutable`: The record is posted, and the organization does not allow changes to posted records. - `adjusting_entry_permission_required`: You do not have the permission to post adjusting entries. - `adjusting_entries_disabled`: Adjusting entries are not enabled for the company. - `adjusting_entry_bank_account`: An adjusting entry cannot use a bank or credit card account. - `recurring_adjusting_entry`: A recurring journal entry cannot be an adjusting entry. - `segregation_of_duties_no_substitute_approver`: The approval policy needs an approver other than the creator, and the organization has no other admin. - `posting_date_after_limit`: The organization limits how far in the future a record can be posted. - `tax_not_calculated`: The organization uses manual tax mode with the tax reminder on. A posted record needs calculated tax. - `recurring_template_archived_party`: A recurring template cannot use an archived customer or vendor. - `master_data_unavailable`: The request sets a reference that the app does not offer for this record. It is inactive, archived, a draft, not available to the record's company, in another currency, or the party for the record's own company. title: Error Code type: - string - 'null' error_reason: title: Error Reason type: - string - 'null' required: - errors title: ErrorSchema type: object AccountType: enum: - bank - accounts_receivable - other_current_asset - fixed_asset - unbilled_receivable - deferred_expense - other_asset - investment - accounts_payable - credit_card - deferred_revenue - long_term_liability - other_current_liability - equity - income - cost_of_goods_sold - expense - other_income - other_expense - statistical title: AccountType type: string SystemCurrencies: enum: - AED - AFN - ALL - AMD - ANG - AOA - ARS - AUD - AWG - AZN - BAM - BBD - BDT - BGN - BHD - BIF - BMD - BND - BOB - BRL - BSD - BTN - BWP - BYN - BZD - CAD - CDF - CHF - CLF - CLP - CNY - COP - CRC - CUP - CVE - CZK - DJF - DKK - DOP - DZD - EGP - ERN - ETB - EUR - FJD - FKP - GBP - GEL - GHS - GIP - GMD - GNF - GTQ - GYD - HKD - HNL - HTG - HUF - IDR - ILS - INR - IQD - IRR - ISK - JMD - JOD - JPY - KES - KGS - KHR - KMF - KPW - KRW - KWD - KYD - KZT - LAK - LBP - LKR - LRD - LSL - LYD - MAD - MDL - MGA - MKD - MMK - MNT - MOP - MRU - MUR - MVR - MWK - MXN - MYR - MZN - NAD - NGN - NIO - NOK - NPR - NZD - OMR - PAB - PEN - PGK - PHP - PKR - PLN - PYG - QAR - RON - RSD - RUB - RWF - SAR - SBD - SCR - SDG - SEK - SGD - SHP - SLL - SOS - SRD - STN - SVC - SYP - SZL - THB - TJS - TMT - TND - TOP - TRY - TTD - TWD - TZS - UAH - UGX - USD - UYU - UZS - VES - VND - VUV - WST - XAF - XAG - XAU - XCD - XDR - XOF - XPD - XPF - XPT - YER - ZAR - ZMW - ZWL title: SystemCurrencies type: string Category1099: enum: - NEC-Box 1 - MISC-Box 1 - MISC-Box 2 - MISC-Box 3 - MISC-Box 4 - MISC-Box 5 - MISC-Box 6 - MISC-Box 8 - MISC-Box 9 - MISC-Box 10 - MISC-Box 11 - MISC-Box 12 - MISC-Box 14 - MISC-Box 15 - INT-Box 1 - INT-Box 2 - INT-Box 3 - DIV-Box 1a - DIV-Box 1b - DIV-Box 2a - DIV-Box 2b - DIV-Box 2c - DIV-Box 2d - DIV-Box 2e - DIV-Box 2f - DIV-Box 3 - DIV-Box 4 - DIV-Box 5 - DIV-Box 6 - DIV-Box 7 - DIV-Box 8 - DIV-Box 9 - DIV-Box 10 - DIV-Box 12 - DIV-Box 13 title: Category1099 type: string MonetaryDistinction: enum: - monetary - non_monetary title: MonetaryDistinction type: string AuditActorSchemaOut: description: Schema for audit actor information. properties: actor_type: title: Actor Type type: - string - 'null' email: title: Email type: - string - 'null' first_name: title: First Name type: - string - 'null' last_name: title: Last Name type: - string - 'null' via: title: Via type: - string - 'null' agent_id: title: Agent Id type: - integer - 'null' agent_name: title: Agent Name type: - string - 'null' timestamp: title: Timestamp format: date-time type: - string - 'null' title: AuditActorSchemaOut type: object ApproverDictSchema: description: Approver info from pre-serialized dict. properties: id: title: Id type: integer first_name: title: First Name type: string last_name: title: Last Name type: string email: title: Email type: string full_name: title: Full Name type: string avatar_url: title: Avatar Url type: - string - 'null' required: - id - first_name - last_name - email - full_name title: ApproverDictSchema type: object RejectedBySchema: description: Schema for rejector information including rejection reason. properties: id: title: Id type: integer first_name: title: First Name type: string last_name: title: Last Name type: string email: title: Email type: string full_name: title: Full Name type: string rejection_reason: title: Rejection Reason type: - string - 'null' required: - id - first_name - last_name - email - full_name - rejection_reason title: RejectedBySchema type: object SystemAccountNames: enum: - Accounts Receivable - IC Accounts Receivable - IC Due From - Vendor Deposits - Undeposited Funds - Unapplied Cash Payments - Accumulated Depreciation - Accounts Payable - IC Accounts Payable - IC Due To - Customer Deposits - Tax Payable - Accrued Purchases - Deferred Revenue - Unapplied Cash Receipts - Cumulative Translation Adjustment - Elimination - Cumulative Translation Adjustment - Retained Earnings - Net Income - Realized Gain/Loss - Unrealized Gain/Loss - Matching Gain/Loss - Rounding Gain/Loss title: SystemAccountNames type: string ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.