AP Create Payment Error - You are not authorized create invoice

Hi @ronhu 

Has the user been added as an invoice payment authorizer?

Best Regards,

Tharindu

@Tharindu Nadeeshan  Thank you for your reply.

you mean below screen? this is the current setting we have for below screen. normally we approve the invoice payment in the invoice workflow, i.e. posting proposal, so we have auto payment approval at final posting and all approver is set to “*”. i don’t think this is the one.

Have you done this process before?   What’s new / what changed? 

I think your Invoice Payment Authorizers is OK, and should not be the cause of the error. 

If you're testing this for the first time, (and this is a test environment) try using the AC user group as your default.  I’m wondering if for some reason the error message is in accurate, meaning some user group / voucher type / voucher series could be the real reason for the error. The user group AC, by default has access to all the things you need for that transaction (in terms of the accounting rules controls). 

The other suggestion is review the details - see what records are listed.  In the details, is anything unique / new / the possible cause of this error.  

If this has worked previously then what was changed?   Does this create the same error if performed by the application owner?   If not, then it could be security.   

If this is TEST and still getting the error, unauthorize the payment order, remove any suspect records, note the removed records, and try again, then note and remove other records and try again.  

Or trace the error message and that may note the cause.  

Best regards, 

Thomas

@Thomas Peterson Thank you for your reply.

I am the first time testing create payment in this environment. i have changed myself default to AC group for voucher type I, U, and redo a purchase order, invoice, and payment, but still got this error.

I use another financial user ID and do the same, financial ID can do the job successfully. apparently it is user id issue. this financial id is the same setting as mine, default to AC group for voucher type I, U.

is user id involved in the GL transaction control? I wonder?

Hi,

Change your user default - user per user group - set AC as your user group.  The voucher types - should need no change.  Even if a voucher type / voucher series lists multiple user groups that default yes or no, does not act in that way. The default user group simply implies that If you do a U voucher type, and your user group is A, or B or C that voucher type (within that function group) would be the default voucher type for that given user group.    In IFS you could hypothetically create voucher types U1, U2, U3 all in the same voucher group (U).  One of those U, U1, U2, U3 should be default for the user various groups.  If hypothetically, your organization has never created new voucher types, then “generally” the voucher series per voucher type with the user groups listed, should all be set as yes for the default.  Generally -     Not suggesting you make changes; your organization may have a valid reason for a different set up.    If you have users who need to constantly enter a voucher type for a given function, then that set up is a reason.  

The user group your assigned or the user group you may select on a few screens drive the voucher type. I know many have misunderstandings. That’s common.  The default yes / no in that screen is for a given function group and the voucher types available for that function group. 

If your user group (user per user group) is defaulted to AC, and other users can do same also with AC group, then look at security.  

The debug console / system trace may identify the true reason for the error, based on the above, security may be most likely reason for the error. 

Best regards

@Thomas Peterson Thank you for your time.

Let me digest your comments and do more testing.

with debug console on, system says “Security” error.

@Thomas Peterson My user ID can successfully complete the process on another environment, so I am quite sure there is something wrong with my permission set.

Thank you for your time.