Skip to main content
e-conomic becomes invoice-ready after the Sweeply app is installed and three invoice mappings are saved: customer group, product, and layout. A field is preselected when there is only one available option; review it before saving.

Required invoice fields

  • Customer group for new customers
  • Invoice product
  • Invoice layout

Additional payment fields

The clearing and payout accounts must be different.

Install and configure e-conomic

1

Open e-conomic settings

Go to Settings > Customer billing, choose e-conomic, and select Connect e-conomic.
2

Install the Sweeply app

In e-conomic, choose the correct agreement and grant the app access. Return to Sweeply after installation.
3

Map invoice resources

Select the customer group, product, and layout. Set payment deadlines in Sweeply at company or customer level; you no longer select a separate e-conomic payment term. Without an override, e-conomic invoices use eight net days.
4

Configure cash when used

For cash payments, select a customer-payment journal and cash account. For Stripe payments, the journal can be saved without a cash account. The cash account must allow direct entries without mandatory department or unit dimensions.
5

Create a product when needed

Select Create, enter the product code and name, and choose a product group. Creating the product does not save it as the mapping until you save the complete setup.
6

Save and create webhooks

Save the bookkeeping setup, then create the supported e-conomic webhooks. Review Needs attention if an existing foreign callback prevents safe configuration.
7

Configure Stripe separately when used

Open Stripe Connect to select the clearing account, payout account, and payout journal.
After saving the required mappings, the connection is ready to create invoices. Review the connection status and any remaining setup messages before using it for customer billing.
Missing e-conomic roles can fail one operation without marking the whole connection unhealthy. Review the affected mapping and the app’s provider permissions.
Last modified on August 27, 2026