The data structure allows creating split bookings.
Entering such data manually it will be processed "correctly".

But the booking dialog (to create or edit bookings) does not support this.

FA6 is currently in beta1.
Try to update and feedback possible issues to FA team.

Description

I'd like to start by importing bookings. However, I can not

• Select an account to import into (probably because I do not have an import config)
• I can't seem to find a way to create an import config for an account
• I cannot select a file/location to import from

Steps to reproduce

1. Open SimpleAccounting
2. Select Project --> New to create a new project
3. Click Actions --> Import Bookings
4. No way to select an account
5. No way to select where to import from

Expected behaviour

1. Open SimpleAccounting
2. Select Project --> New to create a new project
3. Click Actions --> Import Bookings
4. Select an account from teh dropdown
5. Select a file to import from
6. Click Book partially or Bool all to import

Screenshots

Environment

• OS: Windows 10 Pro 20H2 Vuild 19042.867
• SimpleAccounting Version 2.1.0
• .NET SDKs installed:
  • 5.0.103 [C:\Program Files\dotnet\sdk]
  • 5.0.201 [C:\Program Files\dotnet\sdk]
• .NET runtimes installed:
  • Microsoft.AspNetCore.All 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  • Microsoft.AspNetCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  • Microsoft.AspNetCore.App 3.1.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  • Microsoft.AspNetCore.App 5.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  • Microsoft.AspNetCore.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  • Microsoft.NETCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  • Microsoft.NETCore.App 3.1.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  • Microsoft.NETCore.App 5.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  • Microsoft.NETCore.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  • Microsoft.WindowsDesktop.App 3.1.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  • Microsoft.WindowsDesktop.App 5.0.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  • Microsoft.WindowsDesktop.App 5.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Currently the text for the opening booking, generated with "close year" get just numbered.
There could be an option to generate the text including the account name.

The GUI is currently fixed in German.
Add translation, at least for English.

The remote account (of type carry forward) is currently selected automatically.
If the project has multiple carry forward accounts it should be selectable.
Further the text for the created booking entries should be changable.

When changing start date in import dialog, bookings already exists are identified.
When importing these data, the existing booking will be duplicated with the text <already booked> - ....
Such entries must not be imported again.

The initial folder for the file dialog is not application specific.
This results in unexpected initial folder due to other applications activities.

The import folder should be stored in project settings (Setup/Behavior) and restored.

I selected CurrencyTextBox for the booking dialog.
But the behavior is still "curios"...
Find a replacement or implement "manually".

While importing higher number of booking the application temporary does not respond.
After pressing "book" or "book partially" "nothing" happens.
After few seconds the import is completed successfully.

It may be related to the number of entries in the booking dialog
or related to the number of bookings already available.

When importing many bookings the dialog is resized automatically.
This results in very large (tall) dialog.

There should be a good balance between width and high.
This may not change after loading data.

We do not have an accounting software with auditing trail.
We can and we want to be able to change all existing bookings, at least as long the year is not yet closed.
Therefore the booking dialog should be revised to support exiting existing data.

The automatic update from 2.0.0 to 2.1.0 was not successful. I just saw the PowerShell window, but no update.

May be it is related to the Windows shortcut used.

Without the file SimpleAccounting.deps.json the import of booking will fail with

Could not load file or assembly 'System.Text.Encoding.CodePages, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
The located assembly's manifest definition does not match the assembly reference.

The current extension of the project file is bxml. It was introduced with the first german-only version called "Buchhaltung".
The extension does not apply to the public, international name "SimpleAccounting".

Check the following alternatives:

• axml
• acml
• acxml

Extended.Wpf.Toolkit license gets "complicated".
I would like to use different framework (if still needed).

Steps to reproduce the behavior:

1. Open project
2. Select an account and select "edit"
3. Change the account group (not the type)
4. Check the report "totals and balances" - The account is still assigned to the old group. The accounts list is updated, but reopening the project, the account is still assigned to the old group.

To prevent data loss in case of unexpected exception an auto save option should be added.

It would be great to create a new booking entry based on an existing entry.

maybe together as self-contained application

The account groups can only be changeable directly in the project file (XML).
A dialog should be created to allow creating, changing and deleting account groups.

If the project file is changes externally, the project should be reloaded.
In case of unsaved changes, the user shall decide how to proceed.

Booking entries with the followup flag are emphasized in the year journal.
This visualization is missing in the account journal.

The internal configuration (firm name, location, reports, etc.) can only be changed directly in the database.
A dialog should be added to allow changing existing configuration.

When adding new booking entry using "add booking" dialog, the journal is updated in background.
But if journal is larger than space available in current screen, the new entry is not visible.
This reduces the visual feedback.

If the CSV file to be imported is in reverse order the data will be imported ordered by date. This looks ok.
But if there are multiple entries for one day, they will be imported in (original) reverse order.
This creates booking numbers not matching the order of the original (printed) account sheet.

Currently, only manual check is available.

Steps to reproduce:

1. Create new project
2. Save project (as ...)
3. Close and reopen application

Expected: The saved project will be reopened as the recent project.

Actual: The project does not apear as (any) recent project and will further not opened automatically.

The test coverage should be close to 80% before releasing 2.0.

The dialog to show error messages (e.g. failed to load assembly, like #115) show allow to immediately

1. Copy details to clipboard
2. create email with details
3. create issue with details on github

Caliburn 4 has been release.
I need to check whether it is working with SA.

When importing several books for two (bank) accounts can get complicated if there is at least one cross booking.

Importing first account works fine.

The import assistant starts importing from last booking of the selected account.
If there is a cross booking between first account and second account, the import assistant for the second account may not import books before the cross booking.

Example

• Account 1
  • January => Salary
  • February => Cross booking to Account 2
  • March => Shoes
• Account 2
  • January => CD Shop
  • February => Cross booking from Account 1
  • March => Book Shop

After importing account 1 the account 2 has already received the Cross booking in February.
When importing account 2 the assistant will only show "March, Book Shop". The entry "January, CD Shop" will not be imported.

We need a more intelligent import assistant to check more in detail which booking are already existing. It is not sufficient to just start AFTER last booking.

Some text is hidden in the journal tables.
When the lines are selected, the text gets visible:

When changing the booking year, the account journal should NOT be created for the first account (as default), instead the journal for the currently selected account should be updated.

The current implementation in NumberTextBox does not always allow entering value while it is expected by the user.
The primary intention of this implementation was to ensure only a currency value, but it is sometimes to restrictive.

Account types are not translated to German.

When creating a new account, the first group of accounts is selected.
When changing the group selection to add the new account to the second group, the list of accounts gets corrupted.