Which design pattern for common service

See more:

C#

architecture

Trying to improve my design decisions and would like some assistance on the following;

1. Create a service layer that completes Insert/Update/Delete on a SAP system. Using Unity in my VM to resolve the service. - Done
2. I need a verification layer that first runs a simulation. This is simple done by sending/setting in a RFC parameter IsCommit. This layer will also log any issues that is raised by SAP.

So I dont want to duplicate the code for this layer. But want this layer to run the same code but only add the new RFC Parameter. It will also log any issues raised through the simulation. Any suggestions on my approach? Something like a generic service that resolves the service/ method, sets the IsCommit paramater and then executes the base service?

VM

public static BankAccountVM Save(BankAccountVM bankVM)
        {
            var svc = GlobalContext.Current.Container.Resolve<IBankService>();
            BankAccount bankAccount = bankVM.GetModel();

            svc.Update(bankAccount);
            return bankVM;
        }

Service Layer

public class BankService : BaseService, IBankService
{
    private readonly Common _common;
    private readonly IUnityContainer _container;
    private readonly LookupTextValues _textHelp;

    public bool IsCommit { get; set; }

    public void Update(BankAccount bankAccount)
    {
          //Breakdown bank account into rfc paramters

          if(IsCommit )
          {
               //add IsCommit RFC parameter
          }
    }
}

Verification service?