Skip to main content
Question

Voucher

  • February 16, 2026
  • 3 replies
  • 36 views

Hello All,

 

If the Account is added in the Acquisiton account and for that account Code part demand for the FA_object (Code_E) is not a mandatory.

Can we create a manual voucher for that account without providing the FA_Object(Code_E).

Is it possible?

 

3 replies

Mehmetkilivan
Do Gooder (Customer)
Forum|alt.badge.img+5
  • Do Gooder (Customer)
  • February 16, 2026

From experience, this situation usually depends on Posting Control rather than only the account setup.

Even if Code E (FA Object) is set as Optional in the Chart of Accounts, the system may still require it if the account is defined as an Acquisition Account and linked to Fixed Asset integration.

I would recommend checking three areas:

First, confirm that Code E is truly Optional in the account’s Code String Demand.

Second, review the Posting Control for the posting type used in Manual Voucher. In many cases, the FA Object requirement is coming from Posting Control, not directly from the account definition.

Third, verify whether the account is connected to a Fixed Asset Class as an Acquisition Account. If it is fully integrated with FA, the system design expects the transaction to be created through the Asset Acquisition process rather than manually.

If the intention is to post without creating an asset, you may need to either adjust the Posting Control setup or use a different account that is not tied to FA integration.

So yes, it can be possible, but only if the FA integration and Posting Control configuration allow it. Otherwise, the correct approach would be to use the Fixed Asset acquisition process instead of a manual voucher.


Forum|alt.badge.img+19
  • Superhero (Employee)
  • February 16, 2026

Hi, 

Sorry. 

Yes, you must have a FA object ID.   Once registered as an acquisition account, that account must have an FA object.   Q vouchers may be the exception, but regular use of Q vouchers are not recommended, so no you cannot have a entry without the FA object. 

You will receive 

Code part demands are not the driver of this error; FA accounts are special. Once logged as an acquisition account, those accounts are now seen as special, in a way, they are special like a ledger account. Different uses, different reasons, but once marked as such. they are special. 

 

Best regards, 

Thomas


Forum|alt.badge.img+8

Once you setup an account as acquisition account, it is indeed special account and user always need to enter an object ID.  If you mistakenly entered this account as an Object account and now no way to get out of this, better to create new account for alternative usage.